home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
programs
/
proflex2.zip
/
PROFLEX.DOC
< prev
Wrap
Text File
|
1992-11-25
|
198KB
|
4,016 lines
┌─────────┐┌────────┐ ┌─────┐ ┌─────────┐┌──┐ ┌─────────┐┌─┐ ┌─┐
│ ┌────┐ ││ ┌───┐ │ ┌┘ ┌─┐ └┐ │ ┌──────┘│ │ │ ┌──────┘└┐└┐ ┌┘┌┘
│ │ │ ││ │ │ │ ┌┘ │ │ └┐│ │ │ │ │ │ └┐└┐ ┌┘┌┘
│ └────┘ ││ └───┘ └┐│ │ │ ││ └────┐ │ │ │ └────┐ └┐└─┘┌┘
│ ┌──────┘│ ┌────┐ ││ │ │ ││ ┌────┘ │ │ │ ┌────┘ ┌┘┌─┐└┐
│ │ │ │ │ │└┐ │ │ ┌┘│ │ │ │ │ │ ┌┘┌┘ └┐└┐
│ │ │ │ │ │ └┐ └─┘ ┌┘ │ │ │ └──────┐│ └──────┐┌┘┌┘ └┐└┐
└──┘ └──┘ └─┘ └─────┘ └──┘ └─────────┘└─────────┘└─┘ └─┘
Professional Bulletin Board System
Copyright G-A Technologies, Inc. 1992
All Rights Reserved
Shareware Version 1.00
November 1992
TABLE OF CONTENTS i
─────────────────────────────────────────────────────────────────────────────
A BASIC INTRODUCTION
From The Authors . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Trademarks Used . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Beta Test Teams . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Archive Contents . . . . . . . . . . . . . . . . . . . . . . . . . . .4
LICENSING AND REGISTRATION
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Copyright and License. . . . . . . . . . . . . . . . . . . . . . . . .6
How To Register . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . .9
INSTALLATION AND CONFIGURATION
Fast Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Control Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Database Engine . . . . . . . . . . . . . . . . . . . . . . . . . . .16
The File System . . . . . . . . . . . . . . . . . . . . . . . . . . .18
The Message System . . . . . . . . . . . . . . . . . . . . . . . . . .19
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
The BBS Batch File . . . . . . . . . . . . . . . . . . . . . . . . . .21
Multi-Node Operation . . . . . . . . . . . . . . . . . . . . . . . . .22
FidoNet Mailers . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Conversion Utilities . . . . . . . . . . . . . . . . . . . . . . . . .24
Network Support . . . . . . . . . . . . . . . . . . . . . . . . . . .25
SECURITY
Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Security Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Boolean Condition Strings (BCS). . . . . . . . . . . . . . . . . . . .28
MENUS
PFEDMENU: Creating Your Menus . . . . . . . . . . . . . . . . . . . .30
Automatic Menu Execution . . . . . . . . . . . . . . . . . . . . . . .35
File and Message Area Templates. . . . . . . . . . . . . . . . . . . .36
PROFLEX UTILITIES
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
PFCONFIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Modem Configuration . . . . . . . . . . . . . . . . . . . . . . . . .41
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
TABLE OF CONTENTS ii
─────────────────────────────────────────────────────────────────────────────
PFMGR
Area Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Files Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Report Generation . . . . . . . . . . . . . . . . . . . . . . . . . .70
PFMSG
Area Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .71
Echo Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Message Base Support . . . . . . . . . . . . . . . . . . . . . . . . .75
PFUSERS
User Record Management . . . . . . . . . . . . . . . . . . . . . . . .76
PROMAIL
Tossing Mail to ProFlex from ProMail . . . . . . . . . . . . . . . . .79
PFDELMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
SYSOP ADDED FEATURES
Script Language . . . . . . . . . . . . . . . . . . . . . . . . . . .82
REFERENCE
Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . .84
Menu Types And Type Definitions . . . . . . . . . . . . . . . . . . .85
System Operator Keys . . . . . . . . . . . . . . . . . . . . . . . . .101
Textfile Control Codes . . . . . . . . . . . . . . . . . . . . . . . .102
A BASIC INTRODUCTION 1
───────────────────────────────────────────────────────────────────────────
F r o m T h e A u t h o r s
───────────────────────────────────────────────────────────────────────────
With the introduction of Proflex Shareware, 1.00 G-A Technologies offers a BBS
system designed to be easy for a sysop to use without sacrificing features or
performance for the BBS user.
We at G-A Technologies are proud of Proflex Shareware and hope you will be
proud to use it as your Bulletin Board System.
A BBS system is not fixed. Proflex development continues with additional
features being planned for future releases. The Proflex staff at G-A
Technologies wants to hear from you about what features should be given
priority.
The Development Team
A BASIC INTRODUCTION 2
───────────────────────────────────────────────────────────────────────────
T r a d e m a r k s U s e d
───────────────────────────────────────────────────────────────────────────
The products listed below are referenced in this manual and we feel that
proper credit should be given to each for the contribution made to our project
and the computing community as a whole.
BinkleyTerm Bit Bucket Software
BNU David Nugent
Borland C++, Turbo C++, Turbo Pascal Borland International
DESQview Quarterdeck Systems
DoubleDOS SoftLogic Systems
DSZ, ZModem Chuck Forsberg
FrontDoor, TosScan Joaquim H. Homrighausen
IBM, PC-DOS International Business Machines,Inc.
Opus Wynn Wagner III
QuickBBS ---- Unknown ----
RemoteAccess Andrew Milner & Continental Software
TheDraw TheSoft Programming Services
X00 Ray Gwinn
A BASIC INTRODUCTION 3
───────────────────────────────────────────────────────────────────────────
B e t a T e s t T e a m
───────────────────────────────────────────────────────────────────────────
No amount of thanks is sufficient for the individuals who have assisted with
Proflex development. Listed below are the individuals who served on the alpha
and/or beta test teams. Their assistance has been invaluable.
Fred Horner The Private Ear 1:388/10@fidonet
Richard Wallen
Ed Landa
Ed Marquis The Transporter Room 1:379/1@fidonet
Carson Economon The ProFlex Connection 1:379/36@fidonet
John McBade 1:206/2707@fidonet
A BASIC INTRODUCTION 4
───────────────────────────────────────────────────────────────────────────
A r c h i v e C o n t e n t s
───────────────────────────────────────────────────────────────────────────
Proflex Shareware 1.0 File list
btrieve.exe Dos database routines (copyright NOVELL)
bstop.exe Terminates the BTRIEVE record manager and removes it from
memory.
breset.exe Closes all BTRIEVE files from the workstation.
pfconfig.exe Proflex configuration program
pfconfig.cwa
pfconfig.hlp
pfmgr.exe Proflex File Area Manager program
pfmgr.cwa
pfmgr.hlp
pfmsg.exe Proflex Message Area Manager program
pfmsg.cwa
pfmsg.hlp
pfdelmsg.exe Delete message program
pfuser.exe Proflex User File Manager program
pfuser.cwa
proflex.exe Proflex BBS program
english.pfl Proflex English language file
pfedmenu.exe Proflex Menu Editor
promail.exe ProMail mail tosser/scanner
promail.cfg ProMail configuration file
toss.bat Sample bat file for mail tossing
ra2pf.exe RA to Proflex file base conversion program
ra2pfusr.exe RA to Proflex user file conversion program
limits.ctl Sample limits file
events.000 Sample event file
contents.txt contents list
Proflex.doc This documentation
menu.lha Sample menus
text.lha Sample text files
tunes.lha Sample page files
sample.bat A sample BBS batch file
LICENSING AND REGISTRATION 5
───────────────────────────────────────────────────────────────────────────
W A R R A N T I E S
───────────────────────────────────────────────────────────────────────────
By using this software you agree that G-A Technologies in no way assumes
responsibility in any way for the use or misuse of its software. In no way is
G-A Technologies liable for the inability to use any of its products.
G-A Technologies makes no warranty of any kind, either expressed or implied,
and no warranty that the program product is free of errors.
LICENSING AND REGISTRATION 6
──────────────────────────────────────────────────────────────────────────
C O P Y R I G H T N O T I C E
──────────────────────────────────────────────────────────────────────────
Proflex is a copyrighted commercial product of G-A Technologies, Inc., a
privately held corporation with offices located at 1206 Kenilworth Ave.,
Charlotte, N.C. 28204.
Copyright 1992 G-A Technologies, Inc.
All Rights Reserved
Proflex is distributed as four separate products with different license terms
for each product.
P r o f l e x S h a r e w a r e
Proflex Shareware may be evaluated for sixty days without registration in a
non-commercial environment. After sixty days the product must be registered or
the software removed from use.
Proflex Shareware may be distributed under the following terms:
ProFlex may not be modified in any way, for any reason, including but not
limited to de-compiling, disassembling, or reverse engineering of the program.
Copyright notices and version information and all other proprietary program
output must never be altered, removed, bypassed or modified by any means.
You are free to distribute the PUBLICLY AVAILABLE shareware version of ProFlex
to others subject to the above restrictions and also the following:
A. No fee is charged for its use.
B. No remuneration may be accepted for ProFlex. Normal charges for the method
of transmission may be charged.
C. ProFlex must be copied in unaltered form, complete with files containing
license information, the FULL documentation and all accompanying files.
D. All shareware houses/distribution firms must make explicitly clear that
the diskette purchase containing any shareware program has NOT been
registered for use in a commercial environment with G-A Technologies.
Shareware houses and software distribution houses must have a specific
license from G-A Technologies, Inc.
LICENSING AND REGISTRATION 7
──────────────────────────────────────────────────────────────────────
System Operators may make ProFlex available for download only if the above
conditions are met. If the contents of the archive appear altered or not
complete, you may obtain the latest release of ProFlex directly from G-A
Technologies, Inc. You may call the G-A Technologies BBS listed in the Product
Support section of this manual, or mail G-A Technologies a formatted diskette
labled with the word Proflex. Include $5.00 for handling on mail orders.
P r o f l e x R e g i s t e r e d
Registered sysops will receive a new version which will allow use of
additional features such as increased message areas. The registered version
may not be distributed.
A. G-A Technologies authorizes the making of an archival copy of the
registered software for the sole purpose of backing-up your software and
protecting your investment from possible loss.
B. The medium on which the registered software is recorded is transferred to
the customer, but not the title to the software.
C. The customer may resell or distribute unmodified copies of the registered
software provided the customer has purchased from G-A Technologies one copy
of the registered software for each one sold or distributed. The provisions
of this software license shall also be applicable to third parties
receiving copies of the registered software from the customer. In this
case, all media and documentation must be transferred to the purchaser and
the seller retains no rights whatsoever to any part of the software sold.
D. A single copy of the registered version of Proflex may be operated on more
than one computer so long as there is ABSOLUTELY NO POSSIBILITY of it being
used at one location while being simultaneously used at another.
E. G-A Technologies is in no way whatsoever obligated to provide support, or
updates to ProFlex or any other of its software.
P r o f l e x C o m m e r c i a l
The commercial version of Proflex contains printed documentation, maximum
message and file areas are available to the sysop. One year of voice support
and free upgrades is included.
The commercial version may not be distributed and is subject to the same use
restriction as the registered version.
P r o f l e x L A N
Proflex LAN offers all of the features of the commercial version with
additional LAN capabilities for any SPX/IPX or NETBIOS compatible LAN.
The LAN version may not be distributed and is subject to the same use
restriction as the registered version.
LICENSING AND REGISTRATION 8
───────────────────────────────────────────────────────────────────────────
H o w T o R e g i s t e r
───────────────────────────────────────────────────────────────────────────
Those desiring to support the project through registration, those operating
inside a commercial environment, or those who may charge for access to their
bulletin board system should register by one of the following methods.
Proflex v01.00R Registered Version $52.00 US
ProFlex v01.00C Commercial Version $99.00 US
Proflex v01.00L LAN Version 1-10 Nodes $169.95 US
11-100 Nodes $249.95 US
101-250 Nodes $369.95 US
Checks are to be made payable to:
G-A Technologies, Inc.
P.O. Box 31474
Charlotte, North Carolina 28231
USA
Please indicate product and 5.25 or 3.5 inch disks when ordering.
LICENSING AND REGISTRATION 9
───────────────────────────────────────────────────────────────────────────
P r o d u c t S u p p o r t
───────────────────────────────────────────────────────────────────────────
We are very proud of what we've been able to accomplish in bringing ProFlex to
the marketplace. We will do our best to support the product.
Inquiries for support and assistance should be directed to:
G-A Technologies, Inc.
(704) 334-9030 - BBS (Primary)
(704) 334-3282 - Voice
INSTALLATION AND CONFIGURATION 10
──────────────────────────────────────────────────────────────────────
F a s t S t a r t
──────────────────────────────────────────────────────────────────────
A Proflex BBS can be as simple or as complex as the sysop desires. The fast
installation guide is intended to give the new sysop a quick path to a basic
operating BBS. An understanding of the DOS operating system will be assumed.
While the directory structure for Proflex is highly configurable, we will use
some descriptive defaults for this documentation. We will use the C: drive for
all examples. This drive and directory configuration is the default set for
node zero when PFCONFIG is executed with an existing configuration file
Several directories will be needed to organize the system. Let's create this
directory structure for the BBS: (You can change the drive and path names, but
you will need to change the default paths in the configuration.)
C:\PROFLEX\ . . . . . . . . . . . . . For the executables
C:\PROFLEX\FILEBASE\ . . . . . . . . For the files database
C:\PROFLEX\MSGBASE\ . . . . . . . . . For the message base
C:\PROFLEX\USERS\ . . . . . . . . . . For the user database
C:\PROFLEX\TXTFILES\ . . . . . . . . For ANSI/ASCII text files
C:\PROFLEX\MENUS\ . . . . . . . . . . For the menu files
C:\PROFLEX\PAGE\ . . . . . . . . . . For the paging tune files
Copy the files from the distribution archive into C:\PROFLEX\ and we're ready
to start configuring the system.
Move the *.PAG files to C:\PROFLEX\PAGE\.
Move the *.MNU files to C:\PROFLEX\MENUS\.
Move the *.ANS and *.ASC files to C:\PROFLEX\TXTFILES\.
These directories are defaults for the Proflex configuration program.
The first step is to use the PFCONFIG utility to set the information. All of
the Proflex utilities refer to the file produced by PFCONFIG for the drive
locations to be used for the various Proflex files.
From the C:\PROFLEX directory, execute PFCONFIG. Select the BBS node number
you want to use for your BBS. (Proflex defaults to node zero, if you use any
other number you will have to put the node number on the command line.)
If you are using any different paths than the defaults, select 'Global' from
the menu. You should now have a data entry screen to enter the paths for
Proflex to use.
INSTALLATION AND CONFIGURATION 11
──────────────────────────────────────────────────────────────────────
Important: The CWorthy user interface uses <ESC> to leave a form without
saving the information. To save information <ENTER> will leave a field being
edited if one is being modified, and <ENTER> will exit the data entry screen
and save the data. (We are not happy with this user interface and it is being
replaced: see PROFLEX UTILITIES: User Interface.) Be sure that you are not
exiting the data entry screen without the entered information being saved.
From the top PFCONFIG menu select 'Information'. From the submenu, select
'Site Information'. On this data entry screen you can name the BBS and enter
the sysop name the users will see.
Return to the top menu and select 'Modem Configuration'. The four data entry
screens listed in the submenu need to be checked to see if they match your
modem and hardware configuration. Be sure and set 'Answer The Phone' to yes.
With a text editor (Edlin will work if nothing else is available) create a
batch file. In this batch file we need to load the proper Btrieve database
engine and set an operation loop. A basic batch for a DOS stand alone system
file can be expanded from:
C:
CD \PROFLEX
SET PROFLEX=C:\PROFLEX\
BTRIEVE /U:4 /P:4096 (DOS Stand alone only)
:START
BRESET
PROFLEX
IF ERRORLEVEL 8 GOTO EXIT
IF ERRORLEVEL 7 GOTO MAIL
IF ERRORLEVEL 6 GOTO ECHO
IF ERRORLEVEL 5 GOTO NET
IF ERRORLEVEL 1 GOTO LOCAL
IF ERRORLEVEL 0 GOTO EXIT
:NET
REM NETMAIL PROCESSING HERE
GOTO START
:ECHO
REM ECHOMAIL PROCESSING HERE
GOTO START
:BOTH
REM PROCESSING OF BOTH HERE
GOTO START
:LOCAL
PROFLEX -L
GOTO START
:EXIT
INSTALLATION AND CONFIGURATION 12
──────────────────────────────────────────────────────────────────────
The batch file starts by selecting the drive and path to insure that Proflex
is in the current working directory. Next, a PROFLEX environmental variable is
set. The PROFLEX variable is not required for single line use. Now the
Btrieve database used by Proflex is loaded. A reset is given to the database
engine after the loop label. This reset is performed in case a user dropped
carrier and a database was left open. Proflex is called with no arguments,
which will default to online with node zero. Proflex exits with an errorlevel
if mail is entered. The batch file ends with empty loops showing how these
errorlevels can be used to control processing.
Now executing the batch file will place a minimally configured, but
functioning, Bulletin Board System online. As a sysop this is just the
beginning as Proflex offers a multitude of configuration options to turn this
default system into your own personal BBS. The first step on this road is to
step through all of the Proflex utilities with the documentation in hand to
set the configuration to the style of BBS desired by the sysop.
INSTALLATION AND CONFIGURATION 13
──────────────────────────────────────────────────────────────────────
N e w I n s t a l l a t i o n
──────────────────────────────────────────────────────────────────────
Proflex installation can be ten minutes or in ten days, depending on the
complexity of the BBS desired by the sysop. Many levels of menus with
intricate animated screens can be created, each taking as much effort and time
as the individual sysop desires.
This section will step a new sysop through the process required to put a high
quality BBS online for his users. The quality and individuality of the system
will depend upon the amount of time dedicated to this task. Also, much of the
enjoyment realized by many sysops is found in the continual improvements to
the BBS.
Testing is always an important part of the process. A second line to call into
the BBS is extremely helpful. Don't wait until the BBS is completed to start
testing. Testing after each group of modifications will help locate any
problems created through those simple errors that confound us all.
The first step is planning. A rough diagram should be drawn of the menu
structure with file areas, message areas, and external files to be shown. A
few minutes of advance planning will produce a BBS with a consistent design,
and a BBS that is easier for the user to navigate.
The second step is to build a minimal BBS by following the 'Fast Start'
instructions. This will initialize the Proflex databases and provide a test
platform for the changes made as the system is built. Frequent testing as the
design is implemented will make finding changes easier for the sysop.
Next, the configuration utility should be used to completely configure the
BBS. It is recommended that the sysop print the documentation and keep it
handy while considering all of the options in the utilities.
After the configuration, PFUSER should be run to start the user database with
the sysop. (Proflex does not require that the sysop be the first user in the
database.)
Run PGMGR to define all of the file areas and include the files to be listed
in each area. Follow with the PFMSG to define the message areas.
Now the real work can begin. Use PFEDMENU to design the menu system. This is
where the planning can really pay off. Using the Menu Command documentation
section select the individual menu commands to use with each option in each
menu. Examining the default menus supplied with Proflex can offer help.
The displayed text file needs to be created. The value of an ANSI drawing
package such as the registered version of TDRAW can not be understated.
The final step of the process is to expand the sample BBS batch file to
operate any other software such as a network mailer.
INSTALLATION AND CONFIGURATION 14
──────────────────────────────────────────────────────────────────────
C o n t r o l F i l e s
──────────────────────────────────────────────────────────────────────
Proflex supports several control (.CTL) files to allow the sysop to keep a
wide variety of operational parameters in easily edited ASCII files. Proflex
looks for these files in the system directory.
HANDLES.CTL is a list of handles which area not to be used by anyone on the
system. Each banned handle should appear on a separate line in the file.
-Not available in Proflex Shareware-
NODECOST.CTL is a text file setting the NetMail costs for users.
Default <cost> Sets the cost for any address not otherwise specified.
Zone <cost> Sets the cost for all addresses in a zone that are not
declared in Net or Node statements.
Net <net> <cost> Assigns <cost> to all nodes in <net> that are not
specified individually.
Node <node> <cost> Assigns <cost> for an individual node.
BADFILES.CTL is a text file containing a list of filenames not to be uploaded.
This list can be used to prevent known virus carriers, trojans, or hacks from
being uploaded. Each filename should be on a separate line.
PHONENUM.CTL is a list of phone numbers which are not allowed to be entered
by a user. The numbers listed in the file can not appear in any portion of
the user's telephone number. Example:
900- (Stops 900-###-#### and ###-900-####)
555-1212 (Stops ###-555-1212)
LIMITS.CTL sets limits for users based on the security level in their user
record. Each line contains complete details of the individual security level's
capabilities. First, examine each parameter in detail.
Parameter 1 : Security Level
Parameter 2 : Time per day (minutes)
Parameter 3 : 300 Baud download KBytes per day
Parameter 4 : 1200 Baud download KBytes per day
Parameter 5 : 2400 Baud download KBytes per day
Parameter 6 : 4800 Baud download KBytes per day
Parameter 7 : 9600 Baud download KBytes per day
Parameter 8 : 14.4K Baud download KBytes per day
Parameter 9 : 16.8K Baud download KBytes per day
Parameter 10 : 19.2K Baud download KBytes per day
Parameter 11 : 24.0K Baud download KBytes per day
Parameter 12 : 38.4k Baud download KBytes per day
Parameter 13 : Kbyte files download ratio
Parameter 14 : File count download ratio
INSTALLATION AND CONFIGURATION 15
──────────────────────────────────────────────────────────────────────
A sample line:
10 120 0 100 200 200 300 400 450 0 0 0 100 20
We have for security level 10 a daily time limit of 120 minutes, no ability to
download at 300 baud, a 100K daily limit at 1200 baud, 200K at 2400 and 4800
baud, 300 K at 9600 baud, 400K at 14.4 Kbaud, 450K at 16.8 Kbaud. Since we do
not have a modem capable of 19.2, 24.0, or 38.4 Kbaud the limit was set to
zero downloads. The user must maintain a 100:1 download/upload ratio measured
in Kbytes and a 10:1 ratio in the number of files transferred.
All security levels used must be defined or no download capability will exist
for users with that access level. A user with an undefined user level will
receive the maximum single log-on time every time he logs on.
TRASHCAN.CTL is a text file of user name that may not log on. This file is NOT
case sensitive. Names that contain any part of the names in the Trashcan file
are not allowed.
VIP.CTL is a text file list of names, one per line. These users will be
announced with a short system bell at logon and the user comment from the user
record added to the status bar.
INSTALLATION AND CONFIGURATION 16
──────────────────────────────────────────────────────────────────────
D a t a b a s e E n g i n e
──────────────────────────────────────────────────────────────────────
Proflex was designed from the start for multi-line use. While the shareware
version lacks some of the direct network support features that will be found
in the commercial version, the heritage shows in the use of a database engine.
A database engine can allow for such features as mail tossing at the same time
as the message database is in use. It also provides a well tested database
system without the problems associated with custom development.
Version 1.00 of Proflex uses the BTRIEVE database engine from Novell. The DOS
stand alone engine is distributed with Proflex under license from Novell.
Sysops using Novell Netware will be able to use the Netware Btrieve module on
the server without loading the DOS engine on each machine. This was one of the
important features in selecting the Btrieve system for use.
Other database engines may be selected for future versions of Proflex.
For a stand alone DOS system, BTRIEVE must be run to load the engine into
memory before starting Proflex. Two command line parameters are important.
/U:4 tells the Btrieve engine what type of compression to use.
/P:4096 tell the Btrieve engine to use a 4K data block size. Proflex uses 4K
data blocks moving messages in and out of the message database.
For a system operating on a Novell Netware network the BTRIEVE NLM should be
loaded on the server. Refer to your Novell documentation for the methods of
doing this. The parameters used on the Proflex Development System are:
On a Netware workstation BREQUEST should be loaded before Proflex.
Novell Netware supplies a BUTIL program that Netware users can use to
manipulate the databases. Refer to the NetWare documentation for the use of
this program. Novell does not allow BUTIL to be distributed with the DOS
engine.
INSTALLATION AND CONFIGURATION 17
──────────────────────────────────────────────────────────────────────
IMPORTANT: Do not use the DOS BTRIEVE engine on a NetWare drive. For Netware
drives, BREQUEST must be used.
┌────────────────────────────────────────────────────────────────────────────┐
│ NetWare Btrieve Setup V5.15 NetWare 386 Loadable Module │
└────────────────────────────────────────────────────────────────────────────┘
╔════════════════════════════════════════════════════════════════════════════╗
║ Current Btrieve Configuration ║
╠════════════════════════════════════════════════════════════════════════════╣
║ Number of open files: 120 ║
║ Number of handles: 240 ║
║ Number of locks: 100 ║
║ Number of transactions: 100 ║
║ Number of files per transaction: 18 ║
║ Largest compressed record size: 32 ║
║ Largest record size:55256 ║
║ Largest page size: 4096 ║
║ Number of sessions: 250 ║
║ Create files as transactional: No ║
║ Logging of selected files: Yes ║
╚════════════════════════════════════════════════════════════════════════════╝
INSTALLATION AND CONFIGURATION 18
──────────────────────────────────────────────────────────────────────
F i l e S y s t e m
──────────────────────────────────────────────────────────────────────
The Proflex file system utilizes the database engine for two databases.
FILES.PF contains the file area information. FILEBASE.PF contains the records
for individual files.
Both databases can be manipulated by the sysop using the PFMGR utility
distributed with Proflex. See the PFMGR section in this documentation for
details on using the program.
The data structures used in the database are available from G-A Technologies
for third party software authors who want to write additional utilities for
use with Proflex.
Both of the database files, and their associated indexes will be created in
the location specified in the configuration.
The file database contains a flag for CD-ROM's. With this flag set the
information in the database is not checked when the file area is displayed.
The file is assumed to exist and the size and date is assumed to be correct.
After all, this information is not likely to change. On downloads, a CD-ROM
file is downloaded directly from the CD-ROM.
-Not available in Proflex Shareware-
In the registered and commercial versions of Proflex, file handling is
provided for offline file requests from the user to the sysop and for files
stored on a tape system.
INSTALLATION AND CONFIGURATION 19
──────────────────────────────────────────────────────────────────────
M e s s a g e S y s t e m
──────────────────────────────────────────────────────────────────────
The Proflex message system is stored in four databases and a binary file.
AREAINFO.PF Btrieve database for Message Area configuration.
MSGTXT.PF Btrieve database for the message text.
MSGHDR.PF Btreive database for header information.
MSGIDX.PF Btrieve database for user last read pointers.
MSGINFO.PF Binary file containing system message counters.
These files and the associated database indexes are kept in the directory set
for the message base. The databases can be manipulated with the PFMSG utility
provided with Proflex. (PFMSG is documented in its own section of this
manual.)
The Proflex message system was designed for the BBS user, with maximum speed
for message searches and reading. Also, the ability to toss messages into the
databases from FidoNet style message packets while the messages are being read
was considered a requirement.
IMPORTANT: This approach has created major problems in message tossing speed.
This is a major concern for the authors and the message base is actively being
revised and a revised version should be released in a few weeks. The
redesigned message base will offer message processing speed as fast as any
other existing system as well as retaining the better features of the present
system.
INSTALLATION AND CONFIGURATION 20
──────────────────────────────────────────────────────────────────────
E v e n t s
──────────────────────────────────────────────────────────────────────
Proflex offers Events as a method of BBS control. A sysop can use an event to
force users offline and have the BBS exit with a specified errorlevel. This
errorlevel can be trapped in the batch file running the BBS to start other
processes.
Proflex events can be set for a specific day of the month or any day of the
week.
Events can easily be entered using the PFCONFIG utility distributed with
Proflex. (See the PFCONFIG section of this documentation.)
INSTALLATION AND CONFIGURATION 21
──────────────────────────────────────────────────────────────────────
T h e B B S B a t c h F i l e
──────────────────────────────────────────────────────────────────────
An important part of a BBS system is the batch file processing that surrounds
the BBS software. The batch file for a stand alone BBS that is not part of a
BBS network such as FidoNet can be very simple. The batch file for a BBS
operating a FidoNet type mailer and processing EchoMail can quickly become
very complex.
The key to these batchfiles is understanding the errorlevel process under DOS.
Every program that is executed sets the DOS errorlevel variable to a value
between zero and 255 when the program exits. The batchfile construct to test
the errorlevel is commonly written at IF ERRORLEVEL ### GOTO [LABEL]. It is
important to remember that the statement is not logically correct. What
happens in batch file processing is if the errorlevel variable is set to the
specified value OR GREATER the statement evaluates as true and the batch
process jumps to the label.
Proflex can be set to exit at selected errorlevels after a user writes a
message, with the errorlevel depending on the type of message. The batch file
can call PROMAIL to process these messages into a file that other FidoNet type
software can understand.
Other errorlevel exits can be set with events, so that the BBS will exit at
the desired time for any clean-up tasks required for the computer system.
The Fast Start section of this documentation contains a skeleton batch file
that can be used at a building block for a new sysop's BBS batch file.
The value of trapping above the desired errorlevel can not be over emphasized,
as DOS programs will exit with an errorlevel of 255 with unknown errors.
INSTALLATION AND CONFIGURATION 22
──────────────────────────────────────────────────────────────────────
M u l t i - N o d e O p e r a t i o n
──────────────────────────────────────────────────────────────────────
Proflex Shareware 1.00 is not intended for multi-node operation. Operation
with BBS node numbers above one is blocked. This allows a sysop to operate a
node online for users and a node for his own local use. (Node 0 and Node 1)
Multi-line operation will be supported in the Registered Version of Proflex.
The Commercial Version of Proflex will be fully LAN aware.
All Proflex utilities look for system paths in the node 0 configuration.
INSTALLATION AND CONFIGURATION 23
──────────────────────────────────────────────────────────────────────
F i d o N e t M a i l e r s
──────────────────────────────────────────────────────────────────────
It is common for BBS's to link together to share message bases and files. Many
of these networks use FidoNet technology mailer programs to screen incoming
calls for network calls and pass the 'human' callers to the BBS.
The PROMAIL Shareware 1.00 release directly supports FrontDoor operation.
PROMAIL will import and export EchoMail messages from the Proflex message
database, creating file attach messages for EchoMail packets and transferring
the netmail into *.msg format.
Additional mail tossers can be utilized to support other types of mailers. As
support for other mailers will be added shortly after 1.00 release, the sysop
should check with the Proflex Support BBS for direct support for other popular
FidoNet technology mailers.
Indirect support for additional mailers may be possible utilizing third party
tossers to handle the messages placed in the netmail directory by PROMAIL.
Proflex can be operated with a mailer by either 'shell to mailer' or 'BBS
batch' methods.
Shelling to the mailer is accomplished by starting Proflex with a command line
parameter '-m[Drive:Path\Filename]', where the path/filename point to the
mailer program to be executed. This method provides the fastest transit from
the mailer to the BBS for the user.
With the shell to mailer method events must be coordinated between the BBS and
the mailer. Additionally errorlevels must be matched between the mailer and
Proflex. If the mailer exits with an errorlevel less than 32 and the
errorlevel is not defined in PFCONFIG, Proflex will exit to the batch file
with this errorlevel.
The BBS batch method involves writing a batch file that calls the mailer, and
then uses the mailer exit errorlevel to go to the appropriate call to the BBS.
This method requires no event coordination between the mailer and Proflex.
INSTALLATION AND CONFIGURATION 24
──────────────────────────────────────────────────────────────────────
C o n v e r s i o n U t i l i t i e s
──────────────────────────────────────────────────────────────────────
C o n v e r t i n g f r o m R e m o t e A c c e s s
RA2PF.EXE is used to convert your AREAS.BBS (File Areas). This one is quick
and dirty. The program needs to either be run from the directory with the
FILES.RA file or a RA environmental variable must be set. The .PF files
generated by the program should be moved to the Proflex files directory.
RA2PFUSR.EXE (Converting Users) RA2PFUSR is used to convert your USERS.BBS
file to PFUSER.SYS. The PFUSER.SYS will be a bit larger than USERS.BBS because
of the additional information which is now kept on the user.
From your PROFLEX system directory, you will need to call the RA2PFUSR program
with the path to your USERS.BBS/USERSXI.BBS files from RA. Let's assume you
have placed ProFlex on the C: drive in a directory called PROFLEX and the
RemoteAccess files are on the C: drive in a directory called RA. The
conversion would be done as follows:
From the directory location of a RA userbase, run RA2PFUSER and move the
USERS.PF to the Proflex users directory.
This will convert all users from RemoteAccess to ProFlex and create a
PFUSER.SYS file in the C:\PROFLEX directory. The original USERS.BBS and
USERSXI.BBS will not be damaged in any way.
Menus are created much in the same way as done in RemoteAccess. Copy any
RemoteAccess menus needed to convert to the Proflex menu directory and
PFEDMENU may be used to modify them for the new BBS.
INSTALLATION AND CONFIGURATION 25
──────────────────────────────────────────────────────────────────────
N e t w o r k S u p p o r t
──────────────────────────────────────────────────────────────────────
ProFlex was written with networks and networking software in mind. Although
direct support for NETBIOS was not included in the shareware release of
Proflex, NETBIOS based systems such as Lantastic should not have any problems
whatsoever supporting ProFlex and the file and record locking system installed.
ProFlex has been tested on Lantastic and Novell NetWare/386 and has operated
without any noticeable flaws. If you operate a network and use ProFlex as the
BBS system of choice, and encounter any problems, please notify us as to what
networking software is used, memory installed, hard drive space, and any other
pertinent information regarding your system configuration.
SECURITY 26
──────────────────────────────────────────────────────────────────────
S e c u r i t y L e v e l s
──────────────────────────────────────────────────────────────────────
One of the continuing concerns of sysops is system security. This security
falls into two areas, protecting the security of the host computer and
restricting the access of groups of users to the areas the sysop intends for
them to use.
Proflex, in any release, has no 'back door' or method of access not documented
for the sysop.
To control access to sections of the BBS, Proflex offers two methods. The
primary method of control for the sysop is User Security levels. There are
65,535 security levels possible.
Each message and file area may have a security level for access. This will
prevent any user with a security level LESS THAN the configured security level
for the area from accessing the area. Security levels can be set for viewing,
downloading, or uploading in file areas. In message areas, security levels can
be set for sysop functions, reading messages, and entering messages. Menu
options can be set to appear only for a specified security level.
By controlling the appearance of menus and menu options the sysop has total
control of the options available for groups of users.
Download capability for each security level can be defined in the LIMITS.CTL
control file. If a user's security level is not listed in the LIMITS control
file the first listing below the user's security level will be used. If there
is no defined security level below the user with a undefined security level,
the user will have no download privileges.
While Proflex offers additional method of control through security flags and
Boolean Control Strings, the additional controls are not required for a fully
functional BBS. It is recommended to a new sysop that the additional security
features be added slowly as understanding grows.
SECURITY 27
──────────────────────────────────────────────────────────────────────
S e c u r i t y F l a g s
──────────────────────────────────────────────────────────────────────
In addition to security levels, flags may be used for a second level of access
control. Flags provide a mask field that can be tested for access to different
features. This mask field does not have to be an exact match. All the bits set
in the security must be set in the user's flags. Additional bits may be set in
the user's flags.
There are thirty-two access flags arranged in four sets of eight individual
flags, each of which can be either ON or OFF. An ON flag is represented by an
"X" or "1", and an OFF flag by a "-" or "0".
Example:
For downloading in area 22, the sysop has specified the following flags:
A Flags 00100100
B Flags 00000001
C Flags 10000000
D Flags 00000000
A user has the following flags:
A Flags 00100100
B Flags 01100001
C Flags 00000000
D Flags 00011100
The only flags that are tested are the ones set in the area configuration.
Four flags are tested for, A3, A6, B8, and C1. The user does not have the
C1 flag, so he is not granted access to area 22.
IMPORTANT: A sysop should set all flags in his own user record.
SECURITY 28
──────────────────────────────────────────────────────────────────────
B o o l e a n C o n t r o l S t r i n g s - B C S
──────────────────────────────────────────────────────────────────────
-Not available in Proflex Shareware-
The BCS is one of the most versatile options of ProFlex. Its use can vary
from security for making certain menu options available only during specified
hours all the way to sending the user a special message on their birthday.
This gives the sysop the ability to run his board the way he want it.
Boolean Control Strings are only available in the Registered and Commercial
versions of Proflex.
BCS Control Codes
NOTE: The lower case "n" denotes that a number should be entered in its' place.
! = NOT
& = AND
| = OR
Ann = Age of user is => nn.
Bnnnn = Baud rate of user is => nnnn.
Cnnnn = Number of calls made by user is => nnnn.
D = Today is the user's birthday
F[A|B|C|D|]n = Flag [A|B|C|D]n is on.
G = Gender is male
I[0|1|2|3] = No graphics|Ansi|Avatar|Both.
Lnnn = Time remaining today is => nnn.
Nnnn = Node number user is on is => nnn
Pnnn = File points remaining is => nnn
Snnnnn = Security level is => nnn
Tnnn = User's time on line is => nnn
V = User has been validated
Ynnn = Time of day is => nnn minutes past midnight
The BCS itself uses simple logic. Let us look at a simple BCS example. Say
that the sysop would like to make a menu option such as downloading only
available after the user has been validated (In RA you would have to create a
different security level for this). We would write the BCS like this.
V (That's right a 'V' is all that's needed.)
OK lets look at a little more complex example. We have an adult section on our
board and we would like only users 18 and older with a security greater than
or equal to 60.
A18&S60
SECURITY 29
──────────────────────────────────────────────────────────────────────
Now we are ready to move on to the "or" statement. It is important to remember
when using an "or" statement to always put the statement in parenthesis (Ex.
T10&S60&(I1|I3)). Failing to do so will result in a syntax error. When a
syntax error occurs a "^" will point to the error in the statement. Now
examine discuss the example.
T10&S60&(I1|I3)
This BCS is read. If the caller has been online for ten or more minutes and
has a security of 60 or greater and has either Ansi or Avatar graphics on, the
menu item is available.
MENUS 30
──────────────────────────────────────────────────────────────────────
P F E D M E N U
──────────────────────────────────────────────────────────────────────
Proflex offers two types of menus, Proflex and RA. Proflex menus are available
with the Registered and Commercial versions of Proflex.
The PFEDMENU utility distributed with Proflex is intended for creating and
maintaining menus for use with the BBS.
╔══ PFEDMENU - Proflex Menu Editor Version 1.00 Beta ══╗
║ ║
║ Select a Menu type and the Directory for MENU files ║
║ ║
║ Menu type: RA ║
║ ║
║ Menu Path: I:\PROFLEX\MENUS\ ║
║ ║
║ ║
║ ║
║ Ctrl-Enter to accept form ║
╚══════════════════════════════════════════════════════╝
Proflex Shareware 1.00 does not support Proflex style menus. This menu type
offers a increased number of menu commands.
╔═════════════ PFEDMENU - Proflex Menu Editor Version 1.00 Beta ════════════╗
║ ║
║ Current File I:\PROFLEX\MENUS\<NONE>.MNU ║
║ ║
║ ║
║ ║
║ ┌Select option───────┐ ║
║ │▓│Create NEW menu │ ║
║ │░│Edit Existing Menu│ ║
║ │░│Quit │ ║
║ └────────────────────┘ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════╝
At the second screen the sysop chooses to create a new menu or to edit an
existing menu. If the sysop chooses to edit an existing menu, a list of all
files in the menu directory is displayed for selection.
MENUS 31
──────────────────────────────────────────────────────────────────────
╔═════════════ PFEDMENU - Proflex Menu Editor Version 1.00 Beta ════════════╗
║ ║
║ Current File I:\PROFLEX\MENUS\TESTMNU.MNU ║
║ ║
║ ┌ Menu Items ──────────────┐ ║
║ │ │ │ ║
║ └──────────────────────────┘ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════╝
To build a new menu, the sysop is provided an empty menu screen. There are
several general concepts to remember.
Any file to be displayed should be given the automatic execute flag. The order
of automatic execution is top to bottom.
It is very important that there are no conflicts between hot keys. With a
conflict, unless it is resolved by security considerations, the first menu
item with the hot key is executed.
If there is a default menu, it can be disabled by not placing a command in the
display field. In doing this, the display of the menu choices is done by the
sysop with a text file.
For a new sysop, a study of the menu types in the REFERENCE section of this
manual is highly recommended. The samples menus included with Proflex are
another source of help for the sysop.
MENUS 32
──────────────────────────────────────────────────────────────────────
╔═════════════ PFEDMENU - Proflex Menu Editor Version 1.00 Beta ════════════╗
║ ║
║ Current File I:\PROFLEX\MENUS\TESTMNU.MNU ║
║╔══════════════════════════════ Menu Item Edit ════════════════════════════╗
║║ ║
║║ ║
║║ ║
║║ Displayed Text: ║
║║ Optional Data: ║
║║ Menu Type: 0 Display ║
║║ Hot Key: ║
║║ Automatic: NO ║
║║ Color 0 SAMPLE ║
║║ SECURITY 0 ║
║║ FLAGS-A -------- ║
║║ FLAGS-B -------- ║
║║ FLAGS-C -------- ║
║║ FLAGS-D -------- ║
║║ ║
║║ Ctrl-Enter to accept ESC to ABORT ║
║║ ║
╚║ ║
╚══════════════════════════════════════════════════════════════════════════╝
The parameters for each menu item can be displayed by placing the cursor on
the menu item and using <ENTER>.
DISPLAYED TEXT is the text to be displayed for the menu item. If a ANSI/ASCII
screen is to be displayed with this menu, the displayed text should be left
blank.
OPTIONAL DATA is the text file or parameters for the menu item.
MENU TYPE is the menu type for the item. The menu type can be entered as a
number or selected from a list by using the space bar.
HOT KEY is the key to be associated with the command.
AUTOMATIC is a yes/no choice for the automatic execution of the menu item
without the user making a selection.
COLOR is the color to be used on the menu item. If there is no display text
there is no need to select a color. The color can be selected by number or
from a menu using the space bar.
SECURITY is the minimum security level for this menu item to be displayed.
FLAGS are the flags the user must have for the menu item to be displayed.
MENUS 33
──────────────────────────────────────────────────────────────────────
╔═════════════ PFEDMENU - Proflex Menu Editor Version 1.00 Beta ════════════╗
║ ║
║ Current File I:\PROFLEX\MENUS\TESTMNU.MNU ║
║ ║
║ ║
║ ┌Select file───────────────────────┐ ║
║ │▓│ MESSAGES.MNU 3173 11-05-92│ ║
║ │░│ GLOBAL.MNU 1503 09-18-92│ ║
║ │░│ GOODBYE.MNU 501 03-03-90│ ║
║ │░│ MAIN.MNU 4008 11-23-92│ ║
║ │░│ TOP.MNU 334 09-18-92│ ║
║ │░│ SYSOP.MNU 1837 11-20-92│ ║
║ │░│ GOODBYE2.MNU 501 08-19-92│ ║
║ │░│ FILES.MNU 3507 11-04-92│ ║
║ │░│ CHANGE.MNU 2505 11-05-92│ ║
║ │░│ TESTMNU.MNU 334 11-23-92│ ║
║ └──────────────────────────────────┘ ║
║ ║
║ ║
║ ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════╝
Editing an existing menu is done by selecting a menu from a list presented
when a choice is made at the main program menu to edit an existing menu.
MENUS 34
──────────────────────────────────────────────────────────────────────
╔═════════════ PFEDMENU - Proflex Menu Editor Version 1.00 Beta ════════════╗
║ ║
║ Current File I:\PROFLEX\MENUS\MAIN.MNU ║
║ ║
║ ┌ Menu Items ─────────────────────────────────────────────────────────┐ ║
║ │ │ MAIN MENU: │ │ │ │ ║
║ │ │ │ │ │ │ ║
║ │ │ ^M)^essage section │ M │ Gosub menu │MESSAGES │ ║
║ │ │ ^F)^ile section │ F │ Goto menu │FILES │ ║
║ │ │ ^L)^ogoff (Goodbye) │ L │ Gosub menu │GOODBYE │ ║
║ │ │ ^S)^tatistics │ S │ Display │STATS │ ║
║ │ │ ^B)^ulletin info │ B │ Bulletin │BULLET │ ║
║ │ │ ^Y)^ell at Sysop │ Y │ Page SYSOP │Yelling at Sysop ... │ ║
║ │ │ ^C)^hange Setup │ C │ Gosub menu │CHANGE │ ║
║ │ │ ^U)^ser list │ U │ User list │ │ ║
║ │ │ ^N)^ews │ N │ Display │NEWS │ ║
║ │ │ ^V)^ersion │ V │ Version │ │ ║
║ │ │ ^T)^odays callers │ T │ Today's │ │ ║
║ │ │ ^H)^ours used │ H │ Usage │ │ ║
║ └─────────────────────────────────────────────────────────────────────┘ ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════╝
Once an existing menu is selected, the menu is displayed. Each menu item can
be examined in detail by placing the cursor on the item and using the <ENTER>
key.
ALT-F5 displays the menu as defined. All choices are displayed, regardless of
security.
MAIN MENU:
M)essage section F)ile section L)ogoff (Goodbye) S)tatistics
B)ulletin info Y)ell at Sysop C)hange Setup U)ser list
N)ews V)ersion T)odays callers H)ours used
W)ho Is On-Line O)utside
MENUS 35
──────────────────────────────────────────────────────────────────────
A u t o m a t i c C o m m a n d E x e c u t i o n
──────────────────────────────────────────────────────────────────────
A menu function would normally be activated when a user presses the key that
the sysop has assigned to that function. However, it is possible to cause a
function to be executed automatically as soon as a menu is displayed by
setting the entry to "auto execute". As soon as that menu line set for auto
execute is displayed the function is executed, without the need for the user
to select a hot key.
This is a very useful feature when used with the type 40 menu type, which
displays an ASCII/ANSI text file while checking for hot keys. By setting up
the first line of a menu as a type 40 with automatic execute, as soon as the
menu is used your text file is displayed instead of the normal menu lines.
This allows you to easily design with the help of a program like TheDraw very
elaborate menu displays that contain graphics and extra information about the
user by inserting the special text file control codes. What happens if a user
"passes through" a menu by using a stacked menu command? In some cases you may
want the automatic command to execute, for example to redirect the user to
another menu by automatic execution of a type 1 or 2. On the other hand, if
the command is only for cosmetic purposes (maybe a text file to display some
user statistics) it would be better to skip the command and continue straight
to the next menu. The rule is that the menu command will only be executed if
it is the first entry in the menu AND it is not a 'display textfile' type
function.
MENUS 36
──────────────────────────────────────────────────────────────────────
M e n u T e m p l a t e s
──────────────────────────────────────────────────────────────────────
Menu templates relieve the sysop of the drudgery of having to make separate
menus for each file area. With the templating system you only have to create
one menu and when you include the /M option (Message Menus) or the /F (File
Menus) in the optional data field the menu will apply to all file or message
areas. A direct result of this is the amount of maintenance that is required
when changing the menus.
When the read option is selected by the user, ProFlex will substitute this for
a message area number. Likewise, where you would specify a full path for a
file function, put a "/F" in the optional data field. ProFlex will replace
this variable with the path to the currently selected file area.
To put a value into one of these two variables, simply put a "/M=<Area
Number>" or "/F=<Area Number>" in the optional data field of a type 1, 2 or 4
menu command. For example, say you set up a message area template menu called
"MSGMENU", using the /M in the optional data fields. Another menu, which you
have set up to list the available message areas, simply consists of type 1 or
2 menu commands to jump to MSGMENU. One menu line looks like this:
<H>S_Modems
This is a type 2 command, which will "gosub" to the MSGMENU menu:
Type : 2
On the optional data line, put the name of the menu to jump to, and also
set the template variable.
Optional Data : MSGMENU /M=45
45 corresponds to the hard disk conference area, as defined in PFCONFIG.
There are two other constructs that work with the template commands. /M=+ or
/F=+ will increment the currently selected template area by one, and /M=- or
/F=- will decrement the currently selected template area by one. RemoteAccess
will automatically scan all file (or message) areas in the specified direction
to determine the next area that the user has been given access.
MENUS 37
──────────────────────────────────────────────────────────────────────
NOTE: When ProFlex fires up, both the file and message template areas default
to area 1, as defined in the proflex configuration. No checking is done to
verify the user's access to this area at log-on, so you should set both file
and message area 1 to either a blank entry, or an area that all users have
access.
There are a number of special characters that you can put in the display line
of a menu which will display certain system information:
~ : Displays time remaining today.
^ : Switches between the normal line colors and the overall menu
highlight colors.
; : Don't display a carriage return / linefeed at the end of the
line.
@ : Displays the name (as defined in configuration) of the currently
selected file template area.
` : Displays the name (as defined in configuration) of the
currently selected message template area.
PROFLEX UTILITIES 38
──────────────────────────────────────────────────────────────────────
U s e r I n t e r f a c e
──────────────────────────────────────────────────────────────────────
The PFCONFIG, PFMGR and PFMSG utilities distributed with Proflex Shareware
1.00 use the Cworthy 2.1 user interface. G-A Technologies is not happy with
this system and has placed a high priority on replacing the utilities with
programs that are easier to use.
The existing user requires understanding several conventions:
<ESC> Back out one level without saving.
<ENTER> Select from menu - at menu.
<ENTER> Leave data entry filed - in data entry field.
<ENTER> Leave data entry screen with save.
F3 Modify datafield
F7 Restore data field
<GREY +> Expand field into subform.
A typical utility starts with a main menu. <ESC> will exit the menu (and the
program), <ENTER> will select the highlighted item on the menu. A submenu may
be the next level down and will respond as the main menu.
A data entry screen will be at the end of the menu structure. When the data
entry screen is displayed, the user is in the form, but not in a datafield.
The cursor is moved from field to field by the TAB key or the arrow keys. A
field may be changed by moving the cursor to the desired field and typing.
This will cause all existing information in the field to disappear. By using
F3 to enter the field, all existing information is retained for editing.
IF A FIELD IS ENTERED AND CHANGED BY ACCIDENT 'F7' WILL RESTORE THE FIELD ONLY
IF IT IS USED BEFORE THE FIELD IS EXITED.
By using the <ENTER> key while no field is currently entered, (twice if a
field is active) the form may be exited and saved. <ESCAPE> will exit a field
and/or the form without saving the changes.
Many items on the data entry screen have a sub-form to enter the appropriate
responses. These sub-forms are used on flag fields and yes/no/ask choices and
may be called by using the Grey Plus key which is normally located in the
numeric keypad.
In a datafield with two choices, any character key will cause the choice to
toggle.
PFCONFIG 39
──────────────────────────────────────────────────────────────────────
P F C O N F I G
──────────────────────────────────────────────────────────────────────
The PFCONFIG program will be our first stop to set up the Proflex system. This
program creates a configuration file that will tell the Proflex software how
to organize the BBS. The first decision is what BBS node is to be configured.
While Proflex Shareware and Registered are intended for single node operation,
multiple line operation is possible.
A notice may be encountered that indicates the configuration file was not
found. PFCONFIG will create the configuration record when this notice is
displayed.
┌───────────────────────────────┐
│ Proƒlex Configuration │
├───────────────────────────────┤
│Node to configure (0..255): 0 │
└───────────────────────────────┘
Enter the node to configure. Node zero is the default without command line
switches.
╔════════════════════╗
║ AVAILABLE OPTIONS ║
╠════════════════════╣
║ Information ║
║ Modem Configuration║
║ Options ║
║ Global ║
║ System ║
║ Configure ║
║ Editor ║
║────────────────────║
║ Register ║
╚════════════════════╝
Like most main menus, this offers a path to lower menus. Each selection will
be shown in turn.
PFCONFIG 40
──────────────────────────────────────────────────────────────────────
P F C O N F I G M e n u - I n f o r m a t i o n
──────────────────────────────────────────────────────────────────────
┌──────────────────────────────────────────────────────────────────────────┐
│ Proƒlex Configuration Editor v01.00.00 │
│ │
│ PROFLEX.EXE v01.00.00 PFMGR.EXE v01.00.00 │
│ PROMAIL.EXE v01.00.00 PFMGR.EXE v01.00.00 │
│ PROTICK.EXE (Pending) BTRIEVE.EXE v05.16.00 │
│ │
│ This software may be used for 60 days without payment. │
│ After that period, any continued use is in violation of │
│ the copyright terms. See documentation for information. │
│ │
│ Press <esc> to continue │
└──────────────────────────────────────────────────────────────────────────┘
This is simply to let you know the current version of all the Proflex
utilities distributed in the package you received.
╔═══════════════════════════════════════════════════════════════════╗
║ SITE INFORMATION ║
╠═══════════════════════════════════════════════════════════════════╣
║ ║
║ Board name Proƒlex Development System ║
║ SysOp name Cary Howell ║
║ City, State Charlotte, North Carolina ║
║ Country USA ║
║ Primary phone (704) 334-9030 ║
║ ║
╚═══════════════════════════════════════════════════════════════════╝
Here you enter the site information, such as BBS name, sysop and location.
PFCONFIG 41
──────────────────────────────────────────────────────────────────────
P F C O N F I G M e n u - M o d e m C o n f i g u r a t i o n
──────────────────────────────────────────────────────────────────────
╔═══════════════════╗
║MODEM CONFIGURATION║
╠═══════════════════╣
║ Address Ports ║
║ Port and Speed ║
║ Commands ║
║ Responses ║
╚═══════════════════╝
This submenu groups all of the modem configuration screens.
╔═══════════════════════════╗
║ PORT ASSIGNMENTS ║
╠═══════════════════════════╣
║ ║
║ COM1 0x3F8 IRQ4 ║
║ COM2 0x2F8 IRQ3 ║
║ COM3 0x3E8 IRQ4 ║
║ COM4 0x2E8 IRQ3 ║
║ COM5 0x000 IRQ4 ║
║ COM6 0x000 IRQ4 ║
║ COM7 0x000 IRQ4 ║
║ COM8 0x000 IRQ4 ║
║ ║
╚═══════════════════════════╝
Normally, a sysop will not need to change any of these addresses or IRQ's. But
if the need arises to meet non-standard hardware configurations the
availability of these choices is imperative, so here they are.
PFCONFIG 42
──────────────────────────────────────────────────────────────────────
╔══════════════════════════════════════╗
║ MODEM PORT CONFIGURATION ║
╠══════════════════════════════════════╣
║ ║
║ ComPort 1 ║
║ UART Buffer (0-16) 0 ║
║ Port speed 19200 ║
║ Port locked Yes ║
║ Answer phone No ║
║ Delay between commands 10 ║
║ Initialization attempts 3 ║
║ Offhook at end of call Yes ║
║ ║
╚══════════════════════════════════════╝
Most of the settings used here are totally dependent on the modem configuration
and modem of your choice.
An incorrect comm port will cause a total failure of the system to respond to
your phone. Be sure that there are no other devices using the interrupt being
used by your modem's comm port.
UART buffers are only utilized with a 16550 UART. The 16550 uses a FIFO (first
in, first out) buffer to reduce the number of interrupts generated and reduce
the possibilities of 'dropped' characters. If you are using a 16550 (highly
recommended with extended memory caches or multi-taskers) the setting should be
a balance of reduced interrupts (high) and a memory function to prevent
dropped characters (low). A setting of 12 is a good starting point for many
systems. This will mean a 92% reduction in interrupts and allows the system to
be four characters behind in responding to the interrupt.
With the data compression techniques used by high speed modems, the data must
be sent to the modem in bursts faster than the data transmission speed.
Locking the comm port allows this to happen. With more traditional 2400 baud
modems this is not required.
If you are using another program to answer the phone, such as a FidoNet
Mailer, you will not want the BBS to answer the phone. (See: Mailer
configuration)
If you do want have the modem automatically answer the phone, Proflex will
operate correctly. This is not a preferred method of operation as the modem
will answer the phone even if the system is experiencing problems.
PFCONFIG 43
──────────────────────────────────────────────────────────────────────
╔══════════════════════════════════════╗
║ MODEM COMMANDS ║
╠══════════════════════════════════════╣
║ ║
║ Init-1 ATZ ║
║ Init-2 ║
║ Busy ATH1M0 ║
║ Hangup ATH0 ║
║ Answer ATA ║
║ ║
╚══════════════════════════════════════╝
The two modem initialization strings are to allow sending two strings to the
modem if the string length becomes a problem with your modem. Most modern
modems will allow the configuration to be stored internally and set by a
recall command such as "ATZ".
Busy is the string sent to the modem when incoming calls are to be blocked. Be
aware that some newer modems do not hold the line 'off hook' for more than a
few minutes.
Hangup is the string sent to the modem with the completion of a call. A
standard pause and "+++" is sent before the hang-up string.
Answer is the string sent to the modem in response to the Ring modem response
set below.
╔═════════════════════════════════════╗
║ MODEM RESPONSES ║
╠═════════════════════════════════════╣
║ ║
║ Init OK ║
║ Busy OK ║
║ Ring RING| ║
║ MNP-Encode ARQ ║
║ 300 CONNECT| ║
║ 1200 CONNECT 1200 ║
║ 2400 CONNECT 2400 ║
║ 4800 CONNECT 4800 ║
║ 9600 CONNECT 9600 ║
║ 12000 CONNECT 12000 ║
║ 14400 CONNECT 19200 ║
║ 16800 CONNECT 16800 ║
║ 19200 CONNECT 19200 ║
║ ║
╚═════════════════════════════════════╝
With the wide variety of modems on the market today, the strings sent from the
modem will vary. Here you tell Proflex what the strings from your modem mean.
PFCONFIG 44
──────────────────────────────────────────────────────────────────────
P F C O N F I G M e n u - O p t i o n s
──────────────────────────────────────────────────────────────────────
╔══════════════╗
║SYSTEM OPTIONS║
╠══════════════╣
║ Messages ║
║ Files ║
║ Restrictions ║
║ Errorlevels ║
║ Colors ║
║ Yell ║
║ New Users ║
╚══════════════╝
The options submenu is where much of the flavor of your BBS is determined.
This is a location you will return to frequently as you develop your Proflex
system.
PFCONFIG 45
──────────────────────────────────────────────────────────────────────
╔═════════════════════════════════════════════════════════════════════╗
║ MESSAGE BASE OPTIONS ║
╠═════════════════════════════════════════════════════════════════════╣
║ ║
║ Check New Mail At Logon Yes ║
║ Full mail check No ║
║ Quote string @> ║
║ External editor quicked *M ║
║ Default origin Proƒlex Development System ║
║ Reply header ║
║ Combined area name Combined Message Area ║
║ Allow message uploads No Return receipt security 0 ║
║ Netmail replies to echo No Crash mail security 64000 ║
║ KillSent netmail Yes File attach security 64000 ║
║ Confirm deletes No Group mail security 64000 ║
║ ║
╚═════════════════════════════════════════════════════════════════════╝
Check New Mail At Logon can be set to Yes, No or Ask. With Yes, the message
base will be scanned for unread messages addressed to the user. With Ask set,
the user will be asked if he would like to check for new mail.
-Not Available In Proflex Shareware-
Full Mail Check allows the entire message base to be searched for unread
messages instead of looking past the last read pointers. This allows messages
to be found that have been missed.
Quote String is the quote string to be used to mark the quoted block.
Translated choices are '@' for upper case sender's initials and '#' for lower
case sender's initials. Any other characters are placed in the string.
ex: @> becomes BC> for a reply to Bill Calvin
ex: #! becomes bc! for a reply to Bill Calvin
External Editor is the command line to use for an external user editor. The
required commands will vary with the external program. The translation formats
can be found under a type seven menu command. Additionally a '*M' will cause
the Proflex system to swap out of memory to allow for minimum memory
configuration operation.
Default Origin is the origin line to use with EchoMail areas when no other
origin line is defined for an area.
Reply Header is a single line to precede a quoted block in a reply. The
translation characters in this string are:
@ Person the original message was addressed to.
# Person who wrote the original message.
' Date of the original message.
~ Time of the original message.
PFCONFIG 46
──────────────────────────────────────────────────────────────────────
Combined Area Name is the name to use with the combined area feature of
Proflex. This area (area 0, do not use area 0 with any message area) will
allow for multiple message areas to be read simultaneously.
NOTE: The selected message areas in the combined area are not retained between
user sessions in the Shareware version.
Allow Message Uploads determines if users are to be permitted to upload a
message.
Return Receipt Security is the security level (and above) at which the
recipient of a message is asked if the return receipt is to be sent. This
allows users and sysops at this level to read the message without
acknowledging that it was received.
-Not Available In Proflex Shareware-
NetMail Replies To EchoMail will allow user to reply to Echomail messages via
a NetMail system if the selection is set to yes.
Crash Mail Security is the security level (and above) at which a user or sysop
can request the CRASH bit in the message header be set. This option allows a
sysop to permit users to send routed NetMail without the expense of direct
calls.
KillSent Netmail is the security level (and above) at which a user or sysop
may specify that a NetMail message will be killed when sent. This may result
in the sysop not seeing NetMail messages sent by the users if users are able
to use the feature.
File Attach Security is the security level (and above) at which a file attach
may be created. Remember that many routing systems do not permit file attaches
and use of them may create direct mail.
Confirm Deletes is a yes/no option to ask is a message should be deleted
before executing the delete command at a message menu prompt.
Group Mail Security is the security level (and above) that can send a message
to everyone in a defined group. The groups are defined by either the group
number in the user record or a flat ASCII file with the extension of .GRP in
the system directory.
PFCONFIG 47
──────────────────────────────────────────────────────────────────────
╔═══════════════════════════════════════════════════════════════════════════╗
║ FILE HANDLING OPTIONS ║
╠═══════════════════════════════════════════════════════════════════════════╣
║ Upload credit factor 1 Show New Files At Logon ║
║ Touch upload dates No Show missing as *MISSING* ║
║ Minimum disk space in Kb 500 Global Area Name Global File Area ║
║ ║
║ DL Hrs Sun 12:00 am to 11:59 pm ║
║ DL Hrs Mon 12:00 am to 11:59 pm DL Hrs Thu 12:00 am to 11:59 pm ║
║ DL Hrs Tue 12:00 am to 11:59 pm DL Hrs Fri 12:00 am to 11:59 pm ║
║ DL Hrs Wed 12:00 am to 11:59 pm DL Hrs Sat 12:00 am to 11:59 pm ║
║ ║
║ ASCII Available YModem/1K-XModem Available ║
║ Kermit Available ZModem/CRC-32 Available ║
║ XModem-CRC Available YModem-g (MNP Only) Available ║
║ ║
║ Single line display format ║
║ FN:12 SZ:8 DT:10 DC:40 ║
╚═══════════════════════════════════════════════════════════════════════════╝
Upload Credit Factor is the time credit to be given for uploads. A factor of
one returns the amount of time used in the upload to the user. A factor of two
would increase the users time available by twice the amount of time used in an
upload.
Show New Files At Logon offers a yes/no/ask configuration for a search for
files added to the system since the last time the user was online.
-Not Available In Proflex Shareware-
Touch Upload Dates is a yes/no option for changing the file date on uploads to
the upload date. Remember that some protocols, such as Xmodem, do not supply
the original file date and the upload date must be used.
Show Missing As asks you for the indicator string to be supplied in the time
and date field space for files that are not found in the disk directory listed
for the file area.
Minimum Disk Space sets a minimum amount of free disk space on the system
drive. Uploads will not be permitted to fill this space.
DL Hrs allows the sysop to select times that the download function will be
disabled.
The internal file protocols may be individually disabled or enabled by the
sysop.
PFCONFIG 48
──────────────────────────────────────────────────────────────────────
Single Line Display Format is the format to be used by the files system for
displaying the files in the files database.
FN:xx File Name and the number of spaces to allow for the file name.
SZ:xx File Size and the number of spaces to allow for the file size.
DT:xx Date/Time and the number of spaces to allow for date and time.
DC:xx Description and the number of spaces to allow for the description.
Note: The description will line-wrap if the total of the fields and the
spaces between the fields are more than the users screen width.
PFCONFIG 49
──────────────────────────────────────────────────────────────────────
╔═══════════════════════════════════╗
║ RESTRICTIONS ║
╠═══════════════════════════════════╣
║ ║
║ Minimum speed 300 baud ║
║ Minimum ANSI speed 300 baud ║
║ ║
║ Slow Baud Times ║
║ ║
║ Sun 12:00 am to 12:00 am ║
║ Mon 12:00 am to 12:00 am ║
║ Tue 12:00 am to 12:00 am ║
║ Wed 12:00 am to 12:00 am ║
║ Thu 12:00 am to 12:00 am ║
║ Fri 12:00 am to 12:00 am ║
║ Sat 12:00 am to 12:00 am ║
║ ║
╚═══════════════════════════════════╝
This data entry screen allows the sysop to set a minimum speed for users to be
allowed to log on and a minimum speed for the users to use ANSI graphics.
Additionally, times that the minimum speed limit can be violated is set by the
sysop to allow slow modems access during selected times.
PFCONFIG 50
──────────────────────────────────────────────────────────────────────
╔══════════════════════════════════════╗
║ ERRORLEVEL OPTIONS ║
╠══════════════════════════════════════╣
║ ║
║ Local 1 ║
║ 300bps 3 ║
║ 1200bps 12 ║
║ 2400bps 24 ║
║ 4800bps 48 ║
║ 7200bps 72 ║
║ 9600bps 96 ║
║ 12000bps 120 ║
║ 14400bps 144 ║
║ 168000bps 168 ║
║ 19200bps 192 ║
║ Netmail Entered 5 ║
║ Echomail Entered 6 ║
║ Netmail/Echomail 7 ║
║ ║
╚══════════════════════════════════════╝
This is a list of errorlevels for use by Proflex. Proflex will read the
errorlevel of the last program and can set the call speed from a mailer
without a complicated batch file.
Additionally, the type of messages entered will cause the errorlevel exit
values set here after the user is offline. These errorlevels can be used to
process only the appropriate type of mail.
PFCONFIG 51
──────────────────────────────────────────────────────────────────────
╔══════════════╗
║COLOR PALETTE ║
╠══════════════╣
║ Normal Text ║
║ Highlighted ║
║ Status Line ║
║ Box Borders ║
║ Text In Box ║
║ Input Text ║
║ File Areas ║
║ Message Areas║
╚══════════════╝
-Not Available In Proflex Shareware-
The colors used on the sysop's screen along with the file system and message
display colors may be individually configured under this menu. The menu will
be available with Proflex 1.1.
PFCONFIG 52
──────────────────────────────────────────────────────────────────────
╔═══════════════════════════════════════╗
║ PAGING OPTIONS ║
╠═══════════════════════════════════════╣
║ Page duration (in secs) 1 ║
║ Maximum page times 2 ║
║ Automatically log chat No ║
║ Suspend time during chat No ║
║ Ask reason for chat No ║
║ Sysop message board 1 ║
║ ║
║ Sunday 12:00 am to 11:59 pm ║
║ Monday 12:00 am to 11:59 pm ║
║ Tuesday 12:00 am to 11:59 pm ║
║ Wednesday 12:00 am to 11:59 pm ║
║ Thursday 12:00 am to 11:59 pm ║
║ Friday 12:00 am to 11:59 pm ║
║ Saturday 12:00 am to 11:59 pm ║
║ ║
╚═══════════════════════════════════════╝
Page Duration allows the page to be set to a shorter duration than the page
sound script.
Maximum Page Times sets the number of times the sysop can be paged by an
individual user in a day.
-Not Available In Proflex Shareware-
Automatically Log Chat set to yes causes all chat sessions to be logged.
-Not Available In Proflex Shareware-
Suspend Time For Chat set to yes allows the user to chat with the sysop
without using his allowed online time.
-Not Available In Proflex Shareware-
Ask Reason For Chat set to yes causes Proflex to ask the user what he wants to
chat about before paging the sysop.
-Not Available In Proflex Shareware-
Sysop Message Board indicates a message area to be used for the user to leave
a message after an unsuccessful page.
Last is a list of days of the week and times to permit sysop pages.
PFCONFIG 53
──────────────────────────────────────────────────────────────────────
╔═════════════════════════════════════════════════════════════════╗
║ NEW USER CONFIGURATION ║
╠═════════════════════════════════════════════════════════════════╣
║ Security 10 ANSI Yes ║
║ A Flags -------- Avatar Yes ║
║ B Flags -------- Clear Screen Yes ║
║ C Flags -------- More Prompting Yes ║
║ D Flags -------- Hot Keys Yes ║
║ Fullscreen Viewer Yes ║
║ Netmail Credit 400 Fullscreen Editor Yes ║
║ Default group 100 IEMSI Support No ║
║ Auto capitalize No Data phone No ║
║ Phone format (###) ###-#### Voice phone No ║
║ Date format MM-DD-YYYY One word names No ║
║ Language Library ENGLISH Handles allowed No ║
║ Subscription days 365 Birthdate No ║
║ Ask for gender No ║
╚═════════════════════════════════════════════════════════════════╝
Security is the user security level automatically granted all new users.
A, B, C, D Flags are the security flags to be set for the new user.
-Not Available In Proflex Shareware-
NetMail Credit is the cost of NetMail the new user can send. The cost for
each message is determined by the cost field in the nodelist.
Default Group is the user group for new members.
Auto Capitalize mandates the capitalization of a user's name.
Phone format is the format for new user telephone numbers.
Date format is the format to use for new user logon dates.
Language Library is the language file to use with new users.
-Not Available In Proflex Shareware-
Subscription days is the number of days until the new user's access to the
system will be stopped.
ANSI is a yes/no/ask option for determining if ANSI screen commands should be
used with the new user's system.
-Not Available In Proflex Shareware-
Avatar is a yes/no/ask option for determining if Avatar screen commands should
be used with the new user's system.
Clear is a yes/no/ask option for determining if Clear Screen screen commands
should be used with the new user's system.
PFCONFIG 54
──────────────────────────────────────────────────────────────────────
More Prompts is a yes/no/ask option for determining if paging with more prompts
should be used with the new user.
Hot Keys is a yes/no/ask option for determining if the new user should start
with hot keys enabled.
-Not Available In Proflex Shareware-
Full Screen Viewer is a ANSI message viewer that keeps a message header on top
of the screen while the message text scrolls underneath. This is a yes/no/ask
option for the type of message viewer to be used by a new user.
Full Screen Editor is a yes/no/ask option for the new user's default message
editor.
-Not Available In Proflex Shareware-
IEMSI Support is a yes/no option for allowing IEMSI commands from a new user.
Data Phone is a yes/no option to ask a new user for a data phone number.
Voice Phone is a yes/no option to ask a new user for a voice phone number.
One Word Names is a yes/no option to allow or disallow single word names with
new users.
Handles Allowed is a yes/no option on asking the new user for a handle in
addition to a user name.
Birthdate is a yes/no option on asking the new user for his or her birthday.
Ask For Gender is a yes/no option on asking the new user their sex.
PFCONFIG 55
──────────────────────────────────────────────────────────────────────
P F C O N F I G M e n u - S y s t e m
──────────────────────────────────────────────────────────────────────
╔═════════════════════╗
║ AVAILABLE OPTIONS ║
╠═════════════════════╣
║ System paths ║
║ Network addresses ║
║ Archiver/Dearchiver ║
╚═════════════════════╝
This submenu allows the sysop to set the paths to the various components of
the Proflex system, any network address used, and the command lines to use
with archivers.
PFCONFIG 56
──────────────────────────────────────────────────────────────────────
╔═══════════════════════════════════════════════════════════════════════════╗
║ SYSTEM PATH DEFINITIONS ║
╠═══════════════════════════════════════════════════════════════════════════╣
║ ║
║ System directory GA2\SYS:PROFLEX ║
║ Message base GA2\SYS:PROFLEX\MSGBASE ║
║ Ext-MsgBase ║
║ File base GA2\SYS:PROFLEX\FILEBASE ║
║ Ext-FileBase ║
║ User base GA2\SYS:PROFLEX\USERBASE ║
║ Textfiles GA2\SYS:PROFLEX\TXTFILES ║
║ Menus directory GA2\SYS:PROFLEX\MENUS ║
║ Netmail directory GA2\SYS:FILES\NETMAIL ║
║ Logfile GA2\SYS:PROFLEX\PROFLEX.LOG ║
║ Paging files area GA2\SYS:PROFLEX\PAGE ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════╝
System Directory is the directory the executable files are kept in. Proflex
keeps the USERON.BBS, WHO.PF, SYSINFO.BBS, EVENTS.###, E_DAY.###,
EXITINFO.BBS, PFCONFIG.###,and DOORINFO1.DEF files in this directory as well
as the executables. Some of these file locations will follow a PROFLEX
environmental variable.
Message Base is the directory to keep the message database.
-Not Available In Proflex Shareware-
Ext-MsgBase is a directory (and drive) used for an extended message base if
drive space becomes a problem.
File Base is the drive and directory for the files database. This is not the
directory that files are kept in.
-Not Available In Proflex Shareware-
Ext-FileBase is a drive and directory used for an extended files database if
drive space becomes a problem.
User Base is the drive and directory for the user database.
Textfiles is the drive and directory for the ANSI and ASCII files to be
displayed with menu commands.
NetMail Directory is a directory to be used for *.MSG NetMail messages.
(With the ProMail tosser NetMail may be kept in the message database in all
versions).
Menus Directory is the drive and directory for the *.MNU files.
Logfile is the drive, path, and filename for the Proflex log file.
Paging files area is the drive and path for the page sound scripts.
PFCONFIG 57
──────────────────────────────────────────────────────────────────────
╔═══════════════════════════════════════╗
║ NETWORK ADDRESSES ║
╠═══════════════════════════════════════╣
║ ║
║ Main Address 1:379/11 ║
║ AKA #1 0:0/0.0 ║
║ AKA #2 0:0/0.0 ║
║ AKA #3 0:0/0.0 ║
║ AKA #4 0:0/0.0 ║
║ AKA #5 0:0/0.0 ║
║ AKA #6 0:0/0.0 ║
║ AKA #7 0:0/0.0 ║
║ AKA #8 0:0/0.0 ║
║ AKA #9 0:0/0.0 ║
║ AKA #10 0:0/0.0 ║
║ ║
╚═══════════════════════════════════════╝
This is a list of all the network addresses to be used in the EchoMail areas.
╔══════════════════════════════════════════════════════════════════════╗
║ ARCHIVERS AND DEARCHIVERS ║
╠══════════════════════════════════════════════════════════════════════╣
║ ║
║ PkZIP pkzip ║
║ PkUnZIP pkunzip -o ║
║ ARC pkarc a ║
║ UnARC pkunpak -o ║
║ PAK pak a ║
║ UnPAK pak e ║
║ ARJ arj a ║
║ UnARJ arj e ║
║ LHA lha a ║
║ UnLHA lha x -e ║
║ ZOO zoo a -a ║
║ UnZOO zoo e -a ║
║ UserDef ║
║ UserDef ║
║ ║
╚══════════════════════════════════════════════════════════════════════╝
This is a list of the archivers and the command line to use with each. This
will be used by the mail tosser, and future features will make use of this
information.
PFCONFIG 58
──────────────────────────────────────────────────────────────────────
╔═════════════════════════════════════════════════════════════════════════╗
║ SYSTEM STRUCTURE DEFINITIONS ║
╠═════════════════════════════════════════════════════════════════════════╣
║ ║
║ Fast logon No Wait after messages 0 ║
║ Check multi-logon No Password retries 3 ║
║ Remote sysop allowed No Password change 30 ║
║ Exclude sysop No Screen blank 30 ║
║ Shell from textfiles No Min. password length 4 ║
║ Log style FrontDoor Login time allowed 120 ║
║ Environment AutoDetect User time online 60 ║
║ ALT-J swapping No Idle timeout 120 ║
║ Password echo * Watchdog message area 1 ║
║ Strict Password No Sysop message area 1 ║
║ Menu type used Proƒlex Screen Length 24 ║
║ Monochrome only No Screen Width 80 ║
║ ║
╚═════════════════════════════════════════════════════════════════════════╝
Fast Logon tells Proflex to not ask for a name in local mode, but simply
request the user's password.
Wait After Messages is the time to pause after system messages. With a time of
zero, the user is asked to press any key to continue.
-Not Available In Proflex Shareware-
Check Multi-Logon decides if Proflex should check that each user is not logged
onto another node when he logs on.
Password Change is the number of log-ons before each user is forced to changed
their password.
Exclude Sysop decides is the sysop is to be listed in the user list and in the
list of users online.
-Not Available In Proflex Shareware-
Screen Blank is the minutes with keyboard input before the local screen is
blanked.
Shell From Textfiles decides if shell commands work in displayed textfiles.
Minimum Password Length set the minimum password that will be accepted by the
BBS. The maximum password length is 14 characters.
Log Style causes Proflex to write Frontdoor or Binkley style logfiles.
Login Time is the time a new user is given to answer all the questions on the
login (reach main menu). The time is in seconds.
Environment is multi-tasking system used (if any). This will cause Proflex to
use the appropriate time slice release.
PFCONFIG 59
──────────────────────────────────────────────────────────────────────
User Time Online is the session time limit. While the users may be allowed
greater daily time through the LIMITS.CTL file, this will be the single
session limit.
Alt-J Swapping enables the BBS to be swapped out of memory by the sysop to
allow other programs to be executed. This does not hang up the phone.
Idle Timeout is the time limit between user input. Proflex will hang up on the
user if there is no input from the user in this number of minutes.
Password Echo is the character to be echoed to the user when a password is
being input.
Menutype Used tells Proflex to use either RemoteAccess type menus or Proflex
menus. Proflex menus are available in the registered version only.
Screen Length is the screen length (number of character rows) of the local
screen.
-Not Available In Proflex Shareware-
Monochrome Only can be used to force monochrome mode on the local screen.
Screen Width is the screen width (number of columns) of the local screen.
PFCONFIG 60
──────────────────────────────────────────────────────────────────────
P F C O N F I G M e n u - C o n f i g u r e
──────────────────────────────────────────────────────────────────────
╔═══════════════════════╗
║ AVAILABLE OPTIONS ║
╠═══════════════════════╣
║ Language Configuration║
║ Events Schedule ║
║ ProMail Configuration ║
║ ProTick Configuration ║
╚═══════════════════════╝
Options from this submenu offer building a custom language file, setting the
BBS events, and configuring the mail tosser.
╔═══════════╗
║ LANGUAGES ║
╠═══════════╣
║ │ENGLISH ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
╚═══════════╝
An English language file is supplied with Proflex. Additional files may be
created by selecting <INSERT> and supplying the language name. A file is
created with the default prompts and then this file is editable to allow for
translations.
PFCONFIG 61
──────────────────────────────────────────────────────────────────────
╔════════════════════════════════════════╗
║ Event List ║
║ # Time SMTWTFS EL DM ║
╠════════════════════════════════════════╣
║ │ 1. 12:01 M WTF 32 0 ║
║ │ 2. 13:00 100 15 ║
║ │ 3. 14:00 M WTF 32 4 ║
║ │ 4. 23:01 M WTF 16 6 ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
║ │ ║
╚════════════════════════════════════════╝
The events list is created by using <INSERT> and entering the requested
information. The events are auto-numbered and may either be set to a day of
the week or the day of the month. Proflex will exit with the set errorlevel to
allow for batch file logic at the day and time indicated.
PFCONFIG 62
──────────────────────────────────────────────────────────────────────
╔════════════════════╗
║CONTROL FILES EDITOR║
╠════════════════════╣
║ VIP.CTL ║
║ TRASHCAN.CTL ║
║ NODECOST.CTL ║
║ BADFILES.CTL ║
║ HANDLES.CTL ║
║ PHONENUM.CTL ║
║ LIMITS.CTL ║
║ PWDTRASH.CTL ║
║ NAMES.CTL ║
║ OTHER ║
╚════════════════════╝
These files may be selected for editing as ASCII text files.
-Not Available In Proflex Shareware-
VIP.CTL is a text file list of names, one per line. These users will be
announced with a short system bell at logon and the user comment from the user
record added to the status bar.
TRASHCAN.CTL is a text file of user names that may not log on. This file is
not case sensitive. Names that contain any part of the names in the Trashcan
file are not allowed.
-Not Available In Proflex Shareware-
NODECOST.CTL is a text file setting the NetMail costs for users.
Default <cost> Sets the cost for any address not otherwise specified.
Zone <cost> Sets the cost for all addresses in a zone that are not
declared in Net or Node statements.
Net <net> <cost> Assigns <cost> to all nodes in <net> that are not
specified individually.
Node <node> <cost> Assigns <cost> for an individual node.
BADFILES.CTL is a text file containing a list of filenames not to be uploaded.
HANDLES.CTL is a list of handles not to be used by anyone on the system.
PHONENUM.CTL is a list of phone numbers not allowed to be entered by a user.
The numbers listed in the file can not appear in any portion of the user's
telephone number. Example:
900- (Stops 900-###-#### and ###-900-####)
555-1212 (Stops ###-555-1212)
PFCONFIG 63
──────────────────────────────────────────────────────────────────────
LIMITS.CTL sets limits for users based on the security level in their user
record. Each line contains complete details of the individual security level's
capabilities. First, examine each parameter in detail.
Parameter 1 : Security level
Parameter 2 : Time per day (minutes)
Parameter 3 : 300 Baud download KBytes per day
Parameter 4 : 1200 Baud download KBytes per day
Parameter 5 : 2400 Baud download KBytes per day
Parameter 6 : 4800 Baud download KBytes per day
Parameter 7 : 9600 Baud download KBytes per day
Parameter 8 : 14.4K Baud download KBytes per day
Parameter 9 : 16.8K Baud download KBytes per day
Parameter 10 : 19.2K Baud download KBytes per day
Parameter 11 : 24.0K Baud download KBytes per day
Parameter 12 : 38.4k Baud download KBytes per day
Parameter 13 : Kbyte files download ratio
Parameter 14 : File count download ratio
A sample line:
10 120 0 100 200 200 300 400 450 0 0 0 100 20
We have for security level 10 a daily time limit of 120 minutes, no ability to
download at 300 baud, a 100K daily limit at 1200 baud, 200K at 2400 and 4800
baud, 300K at 9600 baud, 400K at 14.4 Kbaud, 450K at 16.8 Kbaud. Since we do
not have a modem capable of 19.2, 24.0, or 38.4 Kbaud the, limit was set to
zero downloads. The user must maintain a 100:1 download/upload ratio measured
in Kbytes and a 10:1 ratio in the number of files transferred.
All security levels used must be defined or no download capability will exist
for users with that access level. A user with an undefined user level will
receive the maximum single log-on time every time he logs on.
PFMGR 64
──────────────────────────────────────────────────────────────────────
U s i n g P F M G R - A r e a M a n a g e r
──────────────────────────────────────────────────────────────────────
╔══════════════════════╗
║ Available Options ║
╠══════════════════════╣
║ Area Manager ║
║ File Manager ║
║ Report Generation...║
║──────────────────────║
║ Exit PFManager ║
╚══════════════════════╝
PFMGR is supplied for file area management. Files may be moved, added, and
deleted from the database. All of the information associated with the file in
the database can be edited.
The top menu allows selection between working with the file area definitions,
individual file entries, and generating reports on the files in the database.
PFMGR 65
──────────────────────────────────────────────────────────────────────
╔══════════════════════════════════════════╗
║ Available Areas ║
╠══════════════════════════════════════════╣
║ │<<ASP>> Shareware Files ║
║ │Business Applications ║
║ │Communications ║
║ │Database Files/Utils ║
║ │Desk Top Publishing ║
║ │DOS Help/Utils ║
║ │File Compression/DeCompression ║
║ │File Processing Utils ║
║ │Floppy Disk Utils ║
║ │Games ║
╚══════════════════════════════════════════╝
The area manager selection from the top menu gives a list of all file areas
defined in the database.
The information on individual areas may be viewed or modified by moving the
cursor to the area name and pressing the <ENTER> key. An area may be deleted
by using the <DELETE> key, and an area may be added by using the <INSERT> key.
╔═══════════════════════════════════════════════════════════════════════════╗
║ AREA MANAGER ║
╠═══════════════════════════════════════════════════════════════════════════╣
║ ║
║ Area Number 31 ║
║ Description <<ASP>> Shareware Files ║
║ File Path GA2\SYS:FILES\CDROM\050A ║
║ Area Flags <see list> ║
║ Area Tag ║
║ ║
║ Sec List 2 Sec Upload 5 Sec Download 5 ║
║ A Flags 0000000 A Flags 0000000 A Flags 0000000 ║
║ B Flags 0000000 B Flags 0000000 B Flags 0000000 ║
║ C Flags 0000000 C Flags 0000000 C Flags 0000000 ║
║ D Flags 0000000 D Flags 0000000 D Flags 0000000 ║
║ ║
║ User BCS ║
║ Upload BCS ║
║ SysOp BCS ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════╝
Area Number is set by the sysop to order the presentation of file area names
to the BBS user.
Description is the information to be presented with the area numbers for the
users to identify the area.
PFMGR 66
──────────────────────────────────────────────────────────────────────
FilePath is the drive and path to the files to be included in this area.
Area Flags selects a sub-form for additional area specific information.
Area Tag is the identification to be used with a TICK style file area.
Sec List is the minimum security level for users to view the area. Under this
field the flags which must be set for access to this area are set.
Sec Upload is the minimum security level for users to upload into this area.
Under this field are the flags which also must be set for users to upload
into the area.
Sec Download is the minimum security level for users to download from this
area. Under this field are the flags which also must be set for users to
upload into the area.
╔══════════════════════════════╗
║ AREA FLAGS ║
╠══════════════════════════════╣
║ Allow Uploads ____ ║
║ Allow Private Uploads ____ ║
║ Uploads Unverified ____ ║
║ TIC/FLE File Area ____ ║
║ Tape Directory Area ____ ║
║ SysOp Request Area ____ ║
║ CD-ROM File Area ____ ║
║ Orphan Files _______ ║
║ Missing Files _______ ║
║ Scan Uploads ____ ║
║ Days To Keep ____ ║
║ Move To Area ______ ║
╚══════════════════════════════╝
The area flags menu is accessed from the Area Manager screen with a grey plus
while the cursor is in the Area Flags field.
Allow Uploads is a yes/no option which can block uploads into this areas
without security level consideration.
Allow Private Uploads is to allow or block uploads to a specific individual.
Uploads Unverified is a yes/no option to prevent users from seeing new files
in the area until the sysop verifies them.
PFMGR 67
──────────────────────────────────────────────────────────────────────
TIC/FLE Area indicates to the system if the area is associated with an
automated file transfer system.
Tape directory area indicates if this is a file system source accessed through
a tape drive.
Sysop Request Area indicates if the files for the area are offline, and
request messages to the sysop should be generated for the user.
CD-ROM File Area indicates if the files for the area are located on a CD-ROM
drive. This CD-ROM is not accessed unless a file is to be downloaded.
Orphan Files is a show/ignore option for files located in the file area
directory, but are not included in the files database.
Missing Files is a show/ignore options to set the treatment of files listed
in the database but missing from the file area directory.
Scan Uploads is a yes/no option to execute a virus scanner on the uploaded
files.
PFMGR 68
──────────────────────────────────────────────────────────────────────
U s i n g P F M G R - F i l e M a n a g e r
──────────────────────────────────────────────────────────────────────
╔══════════════════════════════════════════╗
║ Available Areas ║
╠══════════════════════════════════════════╣
║ │<<ASP>> Shareware Files ║
║ │Business Applications ║
║ │Communications ║
║ │Database Files/Utils ║
║ │Desk Top Publishing ║
║ │DOS Help/Utils ║
║ │File Compression/DeCompression ║
║ │File Processing Utils ║
║ │Floppy Disk Utils ║
║ │Games ║
╚══════════════════════════════════════════╝
The File Manager Selection from the PFMGR main menu provides a list of all the
file areas that have been defined. After placing the cursor on the desired
area, <ENTER> will bring up a list of files listed in that area.
╔═══════════════╗
║Available Files║
╠═══════════════╣
║ │4DOS_1.ZIP ║
║ │4DOS_2.ZIP ║
║ │ACTAEON.ZIP ║
║ │ADDRESS.ZIP ║
║ │AFFORD.ZIP ║
║ │ALPHA.ZIP ║
║ │ASP_APL.ZIP ║
║ │ASP4501.ZIP ║
║ │BBMAIL38.ZIP ║
║ │BOXER311.ZIP ║
╚═══════════════╝
After the file list is displayed, <INSERT> will allow the sysop to place
another file in the database, <DELETE> will remove a file from the database,
and selecting a file with the cursor and using <ENTER> will display the
information from the database on the file.
PFMGR 69
──────────────────────────────────────────────────────────────────────
╔════════════════════════════════════════════════════════════════════════════╗
║ FILE MANAGER ║
╠════════════════════════════════════════════════════════════════════════════╣
║ ║
║ Area Number 31 ║
║ Filename 4DOS_1 Ext ZIP Date 3-5-1992 Time 11:56 am ║
║ File Path GA2\SYS:FILES\CDROM\050A ║
║ Short Desc [0] 4Dos version 4.0 1 of 2 (ASP) ║
║ Uploaded By Proƒlex-FAM v1.00 Date Upld 3-5-1992 ║
║ Narrative <grey +> File Size 339137 ║
║ ║
║Right Arrow-Next Field Left Arrow-Previous Field Enter-Save Esc-Abort║
╚════════════════════════════════════════════════════════════════════════════╝
The File Manager data entry screen is used for both adding a file to the area
database and for modifying that information.
The Area Number, File Name, Extension, Date, Time, and Path are set by the
file in question and the file area definition and are not modifiable.
The Short Description is the description shown in file lists.
The Uploaded By shows how the file arrived on the system.
┌───────────────────────────────────────────────────────────────────────┐
│ Narrative │
├───────────────────────────────────────────────────────────────────────┤
│This file was added to the Proƒlex Filebase via Proƒlex-FAM v1.00 from │
│RemoteAccess. There is no additional description beyond the single │
│line entry. │
│ │
│ │
└───────────────────────────────────────────────────────────────────────┘
The narrative is a long description utilized by the Registered and Commercial
versions of Proflex in a one file per display screen method of viewing the
file description. A <GREY +> brings up a sub-form to view the long
description, which may be 1023 characters in length.
PFMGR 70
──────────────────────────────────────────────────────────────────────
U s i n g P F M G R - R e p o r t G e n e r a t i o n
──────────────────────────────────────────────────────────────────────
╔═════════════════╗
║Available Options║
╠═════════════════╣
║ ALLFILES.LST ║
║ MISSING.LST ║
║ DUPE.LST ║
║ NEWFILES.L10 ║
║ NEWFILES.L30 ║
║ TOP_TEN.LST ║
║ TOPFIFTY.LST ║
║ ORPHAN.LST ║
╚═════════════════╝
The Proflex file area manager can produce a variety of reports for the sysop.
ALLFILES.LST: All files in the database, listed by area.
MISSING.LST: A list of all files that are not present in the directory
specified in the configuration.
DUPE.LST: A list of all files duplicated in more than one file area.
NEWFILES.L10: A List of all files added in the past 10 days.
NEWFILES.L30: A list of all files added in the past 30 days.
TOP_TEN.LST: The ten most popular files.
TOPFIFTY.LST: The fifty most popular files.
ORPHAN.LST: A list of all files in the file area directories that are not
found in the files database.
PFMSG 71
──────────────────────────────────────────────────────────────────────
U s i n g P F M S G
──────────────────────────────────────────────────────────────────────
╔═══════════════════╗
║ Available Options ║
╠═══════════════════╣
║ Message Areas ║
║────────────────── ║
║ Exit PF Message ║
╚═══════════════════╝
The Message Area Manager main menu offers a single selection. The selection
brings up a list of all the message areas defined in the message area
database. Once the area list is on screen, the up and down arrows cam move
through the list. <INSERT> will allow the sysop to add an area. After placing
the cursor on the area name <ENTER> will allow the sysop to modify the area
information. <DELETE> will remove an area. <ESCAPE> returns from the list to
the menu.
╔══════════════════════════════════════════╗
║ Available Areas ║
╠══════════════════════════════════════════╣
║ │4DOS ║
║ │4SALE ║
║ │60S_70S_PROGROCK ║
║ │80XXX ║
║ │ABLED ║
║ │ADLIB ║
║ │AI ║
║ │AIDS/ARC ║
║ │AMIGA ║
║│AMIGA_COMMS ║
╚══════════════════════════════════════════╝
PFMSG 72
──────────────────────────────────────────────────────────────────────
╔════════════════════════════════════════════════════════════════════════════╗
║ Message Area Configuration ║
╠════════════════════════════════════════════════════════════════════════════╣
║ No. 2 Name 4DOS ║
║ Area Type Echomail Access Type Public Messages ║
║ Area Tag 4DOS Pass Through ║
║ Linked Addresses <Grey +> ║
║ Origin ║
║ Net Private Echomail No Allow ANSI Yes Allow Handles Yes ║
║ Minimum Messages 0 Max Messages 0 Max Days 0 ║
║ ║
║ Sysop Security 0 Enter Security 0 Read Security 0 ║
║ A Flags 00000000 A Flags 00000000 A Flags 00000000 ║
║ B Flags 00000000 B Flags 00000000 B Flags 00000000 ║
║ C Flags 00000000 C Flags 00000000 C Flags 00000000 ║
║ D Flags 00000000 D Flags 00000000 D Flags 00000000 ║
║ Sysop BCS ║
║ Enter BCS ║
║ Read BCS ║
╚════════════════════════════════════════════════════════════════════════════╝
This data entry screen is used for both a new message area and changing an
existing message area.
NO. is the message area number. No two message areas should have the same
number.
NAME is the description given the message area for the user.
AREA TYPE is a choice for Local, EchoMail or NetMail. <GREY +> will bring up a
pick list for the choices.
ACCESS TYPE is the type of message to be allowed in the area. Private,
Public, and Private and Public are the choices.
AREA TAG is the EchoMail area tag.
PASS THROUGH is a yes no option for marking a pass through area for the
tosser.
LINKED ADDRESSES is used with the <GRAY +> key to access the list of addresses
to echo the area.
ORIGIN is the origin line to be used with the area. Room must be left for the
local address to be added by the software. Eighty characters are the maximum
allowed for origin lines.
PFMSG 73
──────────────────────────────────────────────────────────────────────
NET PRIVATE ECHO MAIL is a yes/no option for moving private messages into
netmail.
ALLOW ANSI is a yes/no option for allowing ANSI characters to be entered by
the user in the area.
ALLOW HANDLES is a yes/no option to allow users to enter messages with
handles in the 'from' field.
MINIMUM MESSAGES is the number of messages to be kept during message area
maintenance, even if other criteria would result in deletions.
MAXIMUM MESSAGES is the maximum number of messages the tosser should put into
this area. If additional messages are entered, older messages are deleted.
MAX DAYS is the number of days before a message is automatically deleted from
the system.
SYSOP SECURITY is the minimum security level and flags a user must have before
the user has sysop privileges in this area.
ENTER SECURITY is the minimum security level and flags a user must have before
the user may enter a message in this area.
READ SECURITY is the minimum security level and flags a user must have before
the user may read messages in this area.
SYSOP BCS is the Boolean Control String that will be executed to control sysop
access.
ENTER BCS is the Boolean Control String that will be executed to control
access to enter a message.
READ BCS is the Boolean Control String that will be executed to control the
ability to read messages in the area.
PFMSG 74
──────────────────────────────────────────────────────────────────────
P F E D M E N U - E c h o L i n k s
──────────────────────────────────────────────────────────────────────
┌────────────────────┐
│ Echo Links │
├────────────────────┤
│ │No Link │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
│ │ │
└────────────────────┘
The EchoMail links are all systems to share this message base.
THE FIRST ADDRESS IN THE LIST MUST BE THE LOCAL ADDRESS TO USE IN THE ORIGIN
LINE.
All other addresses should be entered in ZONE:NET/NODE format.
PFMSG 75
──────────────────────────────────────────────────────────────────────
P F E D M E N U - M e s s a g e B a s e L i m i t a t i o n s
──────────────────────────────────────────────────────────────────────
A Proflex message base has a limitation of 4,294,967,295 messages in
4,294,967,295 message areas. Proflex Shareware has a maximum of 250 message
areas.
In reality, this means the only limitations are the size of your hard disk.
With the Registered and Commercial version, using the extended message base
option, the limitation would be the size of two of your hard disks.
The maximum message size supported in the Proflex message base is 32K. Online
editing is limited to 8K. This message size limitation has been chosen to
prevent problems with other systems, but allow for larger incoming messages.
EchoMail messages can be tossed to 250 other systems from a single message
area.
PFUSER 76
──────────────────────────────────────────────────────────────────────
U s i n g P F U S E R
──────────────────────────────────────────────────────────────────────
╔════════════════════╗
║ User Manager ║
╠════════════════════╣
║ User List ║
║ ────────────────── ║
║ Exit User Editor ║
╚════════════════════╝
The user area manager main menu offers a single selection. The selection
brings up a list of all the users defined in the user database. Once the area
list is on screen the up and down arrows can move through the list. <INSERT>
will allow the sysop to add an user. After placing the cursor on the user name
<ENTER> will allow the sysop to modify the user information. <DELETE> will
remove a user. <ESCAPE> returns from the list to the menu.
╔══════════════════════════════════════════╗
║ User List ║
╠══════════════════════════════════════════╣
║ │Ali Riza ║
║ │Allan J. Mackinlay ║
║ │Allen Chang ║
║ │Allen Finklea ║
║ │Allen Uhlrich ║
║ │Andrew Buddle ║
║ │Andrew Delisle ║
║ │Anthony J. Teri ║
║ │Arnold Sadowsky ║
║ │Art Macdowell ║
╚══════════════════════════════════════════╝
PFUSER 77
──────────────────────────────────────────────────────────────────────
P F U S E R - U S E R R E C O R D
──────────────────────────────────────────────────────────────────────
╔═══════════════════════════════════════════════════════════════════════════╗
║ Proflex User Record Manager ║
╠═══════════════════════════════════════════════════════════════════════════╣
║ 252 Name: Bob Reid Security 5 ║
║ Alias: Group: 1 ║
║ ║
║ City: Charlotte, N.C. Password: Feeder ║
║ Data Phone: 5555555555 Voice Phone: 5555555555 ║
║ First On: Last On: 10-24-92 Time: 11:08 ║
║ Birthday: Expires 02-11-45 Macros: <Grey+> ║
║ Validated: N Sex: M Subscriber: N Display: <Grey+> ║
║ Protected: N Quiet: N Last Pwd Change: 6 ║
║ ║
║ A Flags: 00000000 Kill: Message Info: <Grey+> ║
║ B Flags: 00000000 Time Banked: 0 File Info: <Grey+> ║
║ C Flags: 00000000 Number Calls: 6 ║
║ D Flags: 00000000 Time Today: 4 ║
║ ║
║ Comment: ║
╚═══════════════════════════════════════════════════════════════════════════╝
The user record manager data entry screen allows a sysop to edit all user
parameters for an individual user.
Several items are marked to use a <GREY +> key to access a sub-form.
╔══════════════════════════════════════════════════════════════════════════╗
║ Proflex User Macros ║
╠══════════════════════════════════════════════════════════════════════════╣
║ Macro 1: ║
║ Macro 2: ║
║ Macro 3: ║
║ Macro 4: ║
║ Macro 5: ║
╚══════════════════════════════════════════════════════════════════════════╝
-Not Available In Proflex Shareware-
Users may define macros which can be executed at any menu. These macros are
simply stacked menu selections that are started when the user activates the
macro.
PFUSER 78
──────────────────────────────────────────────────────────────────────
╔═════════════════════════════════════════════════════╗
║ User Display Information ║
╠═════════════════════════════════════════════════════╣
║ Clear Screen: Y Full Screen Editor: N ║
║ More Prompt: Y Screen Width: 80 ║
║ ANSI Capable: Y Screen Height: 24 ║
║ Hot Keys: N ║
║ Avatar: N ║
╚═════════════════════════════════════════════════════╝
The control option for the user's video are selected with the <GREY +> key
with the cursor in the display field.
╔══════════════════════════════╗
║ User Message Information ║
╠══════════════════════════════╣
║ ║
║ NetMail Credit: 0 ║
║ Messages Waiting: 0 ║
║ Messages Sent: 0 ║
║ ║
╚══════════════════════════════╝
A record of the user's message activity is provided by using the <GREY +> key
with the cursor in the Message Info field.
╔═════════════════════════════════════════════════╗
║ User File Area Information ║
╠═════════════════════════════════════════════════╣
║ Ignore Restrictions N ║
║ ║
║ Uploads: 0 100 K ║
║ Downloads: 2 0 K Today: 0 50 K ║
║ ║
╚═════════════════════════════════════════════════╝
A record of the user's files activity is provided by using the <GREY +> key
with the cursor in the File Info field.
PROMAIL 79
──────────────────────────────────────────────────────────────────────
U S I N G P R O M A I L
──────────────────────────────────────────────────────────────────────
As Proflex uses a database system for messages, a mail tosser is required for
Proflex to be used in a BBS network environment.
PROMAIL is provided to place messages from a FidoNet technology message
packet into the Proflex message database and take new messages from the
database and place them in a *.msg file attach suitable for use with
FrontDoor. It may be possible to use other mailers by using an additional
outbound tosser for additional handling.
PROMAIL TOSS is the command line to use to import messages from an incoming
packet into the message database.
PROMAIL SCAN is the command line to use to export messages from the message
base into packets.
PROMAIL 80
──────────────────────────────────────────────────────────────────────
Additional PROMAIL control can be implemented by the PROMAIL.CFG text file. A
sample is provided with Proflex.
;*****************************************************
;* *
;* P R O M A I L . C F G *
;* *
;* SAMPLE ProMail Mail Tosser Configuration File *
;*****************************************************
; path & file name for FD style logfile
; This should be the first option in the config file.
logpath promail.log
; fidonet address (The one you receive mail under)
node 1:379/11
; path to inbound mail dir - where the mailer puts the mail
mailpath g:\borlandc\promail\inbound
; Mailer type Binkley or FrontDoor
; BINKLEY
FD
; unpack mail Note 3 character archiver type
unpack ARC pkxarc -r $ARCNAME
unpack ZIP pkunzip -o $ARCNAME
; line used for PACK mail
pack ARC PKARC -m $ARCNAME $FILENAME
pack ZIP pkzip -m $ARCNAME $FILENAME
; bad echo area
badecho g:\borlandc\promail\badones
; netmail area
netmail 1
; FD netmail dir ( where FD puts netmail messages)
FDnetdir g:\borlandc\promail\fdnet
; path to outbound mail
outbound g:\borlandc\promail\outbound
; To add areas not found in database:
CREATEAREAS
FORWARD-INFO SECTION ; this marks the forward section
;FORMAT
; NODE ARCHIVE-TYPE [ PW PASSWORD] [ BT packet_type]
; where archive type is NONE, ZIP, PAC ...
; where packet_type is NORMAL CRASH HOLD DIRECT
0:0/0 NONE BT NORMAL ; the defaults
1:379/3 NONE
1:379/13 ZIP PW xyz BT HOLD
1:30797/1 ZIP PW xyz BT CRASH
;END-OF-FILE
PROMAIL 81
──────────────────────────────────────────────────────────────────────
P F D E L M S G
──────────────────────────────────────────────────────────────────────
A message area maintainence utility, PFDELMSG, is provided to automatically
delete messages from the message database by the parameters defined in the
message area database.
PFDELMSG [options]
Options: /NOLOG Suppresses logging of the message deletions.
/ZAP n Remove all messages from area n.
The normal delete uses the minimum messages, maximum messages, and the maximum
days in the message area database.
If the number of messages is greater than maximum messages, the oldest messages
are deleted until the maximum messages limit is reached.
If the age of a message is greater than the maximum age limit, messages will
be deleted until the minimum message limit is reached.
The maximum message limit can be disabled by using zero in the area
configuration.
SYSOP ADDED FEATURES 82
──────────────────────────────────────────────────────────────────────
S c r i p t s
──────────────────────────────────────────────────────────────────────
While the most common use of scripts is a new user questionnaire with menu
type 12, the limit of the use of scripts is usually reached with the
imagination of the sysop.
Any line in a script starting with ';' is considered a comment and not
processed.
A maximum of fifty variables can be used. Each variable is named by the
variable number, 1 through 50.
A pipe symbol "|" is used to indicate a carriage return/line feed in any
output requests.
Script commands:
ask <len> <var name> Wait for the user to input a maximum
of 'len' characters and store the
answer in 'var name'. The maximum values
of 'len' is 79.
changecolor <fore> <back> Set the screen foregound and background
color, using the standard IBM numeric
color definitions.
clearscreen <no options> Clears the screen.
display "<text string>" Displays the text string.
endif <no options> End if statement.
getchoice <valid choices> <var name> Wait for the user to input a key from
the 'valid choices' list and store the
response in 'var name'
goto "<LABEL>" Jump to label.
if <var name> = "<text string>" If the contents of 'var name' match the
'text string' display everything between
the if statement and the following
endif.
label "<label string>" Define a label.
listanswer <var name> Listanswer displays the user's answer
stored in 'var name'.
SYSOP ADDED FEATURES 83
──────────────────────────────────────────────────────────────────────
outputanswer "<descriptor>" <var name> Writes the 'descriptor' string and then
the user's answer to the output file.
postinfo <no options> Writes the user, date, and time to the
output file.
quit <no options> End script.
setflag <flagset><flagnum> <ON|OFF> Set the user's 'flagset' flags, flag
'flagnum' to ON or OFF. Flagset is
indicated by A, B, C, or D. Flagnum is
the individual flag, 1-8.
setsecurity <security level> Set the user's security level.
showfile <filename> (no ext) Display file. Eight characters maximum.
.ANS or .ASC extension searched for
depending on the users display
parameters.
waitenter Wait for the user to press <ENTER>.
REFERENCE 84
──────────────────────────────────────────────────────────────────────
C o m m a n d L i n e P a r a m e t e r s
──────────────────────────────────────────────────────────────────────
Proflex offers a variety of command line parameters to allow the sysop to
define the operation of the BBS.
-L Local Logon
-C## Communications Port (if caller online)
-B##### Baud Rate (if caller online)
-E### Errorlevel for Normal Exit (Default in PFCONFIG)
-S Local Output Off (Default ON)
-D Small Status Line (Default OFF)
-N### Node Number (Default 0) (Must be Defined!)
-T#### Time to Next System Event (if caller online)
-F Reset (do not enforcef Forced Events\r\n")
-R Re-admit a user still online (Exitinfo.BBS)
-Mc:\fd\fd.exe Shell to front end mailer mode
REFERENCE 85
──────────────────────────────────────────────────────────────────────
M e n u T y p e s a n d T y p e D e f i n i t i o n s
──────────────────────────────────────────────────────────────────────
The following is a list of the menu types supported when using the ProFlex
style menus. If you are using the RemoteAccess menu types to run ProFlex
without converting to the ProFlex menus, those marked as *NEW* will not be
supported on your system. Note, some menu types have been combined or are not
supported in the RA menu style because of serious duplication of work on the
part of RemoteAccess and have been combined with others to provide easier
handling in ProFlex. These are denoted as *CHANGED* or *DELETED* as
appropriate.
───────────────────────────────────────────────────────────────────────────
Type :1
Name :GOTO Menu
Optional Data :<menu name> [password] [/F=<filearea>|+|-]
[/M=<message area>|+|-]
Comparative :Same as RemoteAccess
This function type allows you to go to another menu from the present one, when
jumping to another menu, the template information may be changed. The Goto
menu has no point of return to the calling menu.
───────────────────────────────────────────────────────────────────────────
Type :2
Name :GOSUB Menu
Optional Data :<menu name> [password][/F=<filearea>|+|-]
[/M=<message area>|+|-]
Comparative :Same as RemoteAccess
This function type allows you to go to another menu from the present one, and
as in the GOTO menu option, the template information may be changed. The Gosub
menu throws the current menu into a stack that can be returned to by using a
type 3 menu.
───────────────────────────────────────────────────────────────────────────
Type :3
Name :RETURN from GOSUB
Optional Data :N/A
Comparative :Same as RemoteAccess
This allows you to return to the calling menu. This only works if a type 2
was issued to get to that menu and you have not issued a type 4, GOTO w/CLEAR.
───────────────────────────────────────────────────────────────────────────
REFERENCE 86
──────────────────────────────────────────────────────────────────────
Type :4
Name :GOTO w/CLEAR
Optional Data :<menu name> [password] [/F=<filearea>|+|-]
[/M=<message area>|+|-]
Comparative :Same as RemoteAccess
This performs the same task as menu type 1 with the exception that if any type
2 menu functions (GOSUBs) were called, this will clear the gosub menu stack
and issuing a type 3 after a GOTO w/CLEAR will cause an error to occur.
───────────────────────────────────────────────────────────────────────────
Type :5
Name :Display ANS/ASC file
Optional Data :<1-8 character filename> [password]
Comparative :Optional password was added.
This menu type will display a file contained in your system textfile
directory. If the user has ANSI on, it will append .ANS to your filename. If
the user does not have ANSI on, or you do not have an .ANS file in your
textfile area, ProFlex will display the .ASC file instead. If both files are
missing, a message will be sent to the user and entered into the logfile.
───────────────────────────────────────────────────────────────────────────
Type :6
Name :Bulletin Menu
Optional Data :<1-8 character filename>
Comparative :Same as RemoteAccess.
The filename specified will be displayed as a type 5 and the user is prompted
for the file to view. I.e. assuming our filename is BULLET, the user is shown
BULLET.ANS/BULLET.ASC depending on their settings. The user is prompted and
they select to view 1. The 1 is appended to BULLET, thus the file BULLET1.ANS
BULLET1.ASC is displayed depending on user's color settings.
───────────────────────────────────────────────────────────────────────────
REFERENCE 87
──────────────────────────────────────────────────────────────────────
Type :7
Name :Spawn Child Process
Optional Data :<command line> [control codes] [/EXIT=n] [/BAUD=xxxx]
Comparative :Some changes from RemoteAccess, upward compatible.
This command will run a program in a shell from ProFlex. ProFlex contains a
smart spawning system which detects EMS/XMS. If their is sufficient RAM
memory available (in either EMS/XMS) ProFlex will swap itself into that
memory, otherwise it will swap to disk. This swap leaves only 735 bytes of
ProFlex in resident memory.
The child process must be an EXE or COM file. To run a batch file, the
command interpreter must be reloaded, your option line would read:
c:\command.com /c monitor.bat
Some door software requires that extra information be passed on the command
line, therefore, ProFlex will allow you to do this with command line codes.
These codes are interpreted when the system prepares to spawn.
*A: Write user's name.
*B: Write user's baud rate, or 0 if local
*C: Full path and name to command.com
Using this would have shortened the line above to:
*C /c monitor.bat
*D: Automatically generate the DOOR.SYS for doorway parameter file.
*F: User's first name.
*G: ANSI graphics, 0=Off, 1=On
*H: The fossil driver is normally deinitialized upon a call to the
spawn but this will force it to remain 'hot' or active.
*L: User's last name.
*N: Line number, as specified by the -N command line parameter.
*Oxxxx: Override the baud rate value passed with xxxx.
*P: Communications port COM1 = 1, COM2 = 2.
*R: User's record number in the user file.
*T: Time remaining for current call.
*!: Freeze the system timer.
*#: Turn off the WANTS CHAT indicator on return from the spawn.
*0: Full path to currently selected file template area.
*1: Number of the currently selected message template area.
REFERENCE 88
──────────────────────────────────────────────────────────────────────
ProFlex also writes EXITINFO.BBS, DORINFO1.DEF as default. These files are
completely compatible with RemoteAccess version 1.01.
The /EXIT=n command is a new feature supporting the use of doors from other BBS
software packages. Here is a list of EXIT codes:
/EXIT=100 : default, RemoteAccess style. /EXIT=204
/EXIT=204 : QuickBBS v2.04 EXITINFO.BBS.
/EXIT=12 : PCBoard v12.0 user file and exit information files are
created.
/EXIT=14 : PCBoard v14.0 user file and exit information files are
created.
/EXIT=3 : WildCat v3.0 user file and exit information files are
created.
The /BAUD=nnnn command is also a new feature supporting locked fossil rates.
The baud rate specified in /BAUD will be placed in DORINFO, EXITINFO and any
other files as required by the /EXIT command.
──────────────────────────────────────────────────────────────────────────────
Type :8
Name :Product Information
Optional Data :N/A
Comparative :Same as RemoteAccess.
Displays the version information, credits, and copyright notice. This
function will also display the level of registration.
───────────────────────────────────────────────────────────────────────────
REFERENCE 89
──────────────────────────────────────────────────────────────────────
Type :9
Name :Logoff user
Optional Data :N/A
Comparative :Same as RemoteAccess.
This function will display the GOODBYE.ANS/ASC file and terminate the current
session. The user is logged off and the system information for that user is
updated.
───────────────────────────────────────────────────────────────────────────
Type :10
Name :System Usage Graph
Optional Data :N/A
Comparative :Same as RemoteAccess.
This will display the system usage graph based on information acquired thus
far on your system and the number of calls per hour.
───────────────────────────────────────────────────────────────────────────
Type :11
Name :Page the sysop.
Optional Data :[filename]|[paging string]
Comparative :New features added, upward compatible
This function will display the paging string or filename to the user. The
default paging song is the theme from "Star Trek". In the configuration you
would have told ProFlex what directory you keep your paging files in. This
system will automatically and randomly pull a paging song (file) and play it.
You may create your own paging songs by creating a file nnnnnnnn.PAG where the
nnnnnnnn can be any eight character or less name. The following keywords are
valid in the file:
TONE [hz] [n/100's sec] sounds hz for duration of n/100's.
WAIT [n/100's sec] sounds nothing for n/100's duration.
The following table lists several musical octaves and the correct frequency
value associated with each note:
Note Oct - 1 2 3 4 5 6
----
C F 45 134 268 536 1071 2145
C# r 71 142 284 568 1136 2273
D e 75 150 301 602 1204 2408
D# q 80 159 319 638 1275 2551
E u 84 169 338 676 1351 2703
F e 90 179 358 716 1432 2864
F# n 95 190 379 758 1517 3034
G c 100 201 402 804 1607 3215
G# y 106 213 426 851 1703 3406
A # 113 225 451 902 1804 3608
A# 119 239 478 956 1991 3823
B 127 253 506 1012 2025 4050
───────────────────────────────────────────────────────────────────────────
REFERENCE 90
──────────────────────────────────────────────────────────────────────
Type :12
Name :Questionnaire
Optional Data :<filename> [/N] [/E]
Comparative :New features added, upward compatible
A script file is used to display the questionnaire. See SCRIPTS.
───────────────────────────────────────────────────────────────────────────
Type :13
Name :User listing
Optional Data :N/A
Comparative :Same as RA
The user is displayed a list of users as listed in the user file along with
their location, file ratio, and the last time they called the bbs.
───────────────────────────────────────────────────────────────────────────
Type :14
Name: :Time
Optional Data :N/A
Comparative :Same as RA
Displays to the user the current time, and date. Additionally the user's daily
time limit, time used, and time remaining are displayed.
───────────────────────────────────────────────────────────────────────────
Type: :15
Name: :Exit to DOS
Optional Data :<Errorlevel>
Comparative :Same as RA
This menu type tells ProFlex to exit to DOS with the errorlevel specified in
the optional data field. This function is used to perform maintains specified
in Batch files. If this menu type is used while a user is online use the -R
parameter to keep the user online (Ex. PF -R). This will cause ProFlex to
return the user to the TOP.MNU.
Note: Errorlevels 0 through 5 are reserved by ProFlex for system use.
───────────────────────────────────────────────────────────────────────────
Type: :16
Name: :Change User's Location
Optional Data :N/A
Comparative :Same as RA
Presents the user the ability to be able to change their location as listed in
their user record.
───────────────────────────────────────────────────────────────────────────
REFERENCE 91
──────────────────────────────────────────────────────────────────────
Type :17
Name :Password Change
Optional Data :N/A
Comparative :Same as RA
Enables the user to change their password. For optimum security it is
suggested that the Sysop encourage the users to change their passwords on a
regular basis. Provisions are made in the PFCONFIG to require the user's to
change their passwords after a specified number of logons.
──────────────────────────────────────────────────────────────────────────
Type : 18
Name : Change Screen Length
Optional Data :N/A
Comparative : Same as RA
Enables the user to change the length of their screen display.
Note: This will affect the use of the "Continue?" prompt.
───────────────────────────────────────────────────────────────────────────
Type :19
Name :Toggle Screen Clearing
Optional Data :N/A
Comparative :Same as RA
Enables the user to select whether or not they would like the system to send
screen clearing codes.
───────────────────────────────────────────────────────────────────────────
Type :20
Name :Toggle Page Pausing
Optional Data :N/A
Comparative :Same as RA
Enables the user to select the option of having page pausing on or off.
───────────────────────────────────────────────────────────────────────────
Type: :21
Name: :Toggle ANSI Graphics
Optional Data :None
Comparative :Same as RA
Lets the user select if they wish to have ANSI graphics sent. The full screen
message editor is disabled if ANSI is disabled.
───────────────────────────────────────────────────────────────────────────
Type :22
Name :Check For Mail
Optional Data :None
Comparative :Same as RA
Checks for new mail that the user hasn't already read. This can also be
implemented at logon by specifying the option in PFCONFIG.
───────────────────────────────────────────────────────────────────────────
REFERENCE 92
──────────────────────────────────────────────────────────────────────
Type :23
Name :Read Messages
Optional Data :<Message Area #> or /M
Comparative :Same as RA
This menu type starts the process of reading mail. The user is first checked
to see if they have read access to the message area. Then they are presented
with 3 different message scanning methods. [TO] - who the message is to.
[FROM] - who the message is from. [SUBJECT] - scans by subject. In the
optional field you may either put /M or put the message area # as specified in
pfconfig.
If you choose to put /M Proflex will automatically put the current menu
template in the selected message area. If you choose to place a # in the
optional data, you have the ability to create a different menu for each
message area.
The following commands are available in a message menu:
[-] :Read previous reply.
[+] :Read next reply.
[A] :Redisplay message.
[N] :Go to the next message.
[L] :Go to the previous message.
[R] :Reply to the message.
[E] :Enter a message in the current area.
[D] :Delete current message (Only the people with sysop access to the area
and the person who the message is to or from may delete messages).
[S] :Stop reading messages.
The following commands are available only to users that have sysop access
to the message area.
[!] : Display ^A kludge lines normally hidden.
[*] : Edit the current message's attributes.
[X] : Export message to a file or the printer.
[/] : Forward message to another user in any area.
[=] : Mark message as unreceived and go to the next message.
[U] : Modify the security level of the user who posted the
currently displayed message, provided the user is listed in the
userfile. Great for "on the fly" user verification!
───────────────────────────────────────────────────────────────────────────
Type :24
Name :Scan Messages
Optional Data :<Message Area #> or /M
Comparative :Same as RA
Basically the same as the READ menu (Type 23) but only the message header of
each message is displayed. When this menu type is invoked the user is given
the option to mark messages for easy retrieval at a later time.If you choose
to put /M PF with automatically put the current menu template in the selected
message area.
───────────────────────────────────────────────────────────────────────────
REFERENCE 93
──────────────────────────────────────────────────────────────────────
Type :25
Name :Quick Scan of Messages
Optional Data :<Message Area #> or /M
Comparative :Same as RA
If you choose to put /M Proflex will automatically put the current menu
template in the selected message area
───────────────────────────────────────────────────────────────────────────
Type :26
Name :Delete Message
Optional Data :N/A
Comparative :Same as RA
Allows the user to delete the current message as long as the following
conditions are met:
1. The user is the author or the recipient of the message area.
2. The user has sysop access to the current message area.
3. The message is contained within an EchoMail and the user is the author of
the message and it has not been exported from the message area.
───────────────────────────────────────────────────────────────────────────
Type :27
Name :Post Message
Optional Data :<Message Area #> or /M [/L] [/T=<Name>]
Comparative :Same as RA
If you choose to put /M Proflex with automatically put the current menu
template in the selected message area. When using the /T parameter make sure
to substitute an underscore "_" for the space between the first and last name
of the person the message to which to message is written.
───────────────────────────────────────────────────────────────────────────
Type :28
Name :Select Combined Areas
Optional Data :N/A
Comparative :Same as RA
Enables the user to select any combination of frequently read message bases
into combined area for convenient reading. The user is presented with a list
of message bases to which they have access to and asked to toggle on or off
the message bases. This combination of message bases is then appended to their
user's record as to be available at their next logon. In order for this menu
to be available the user must go to area "C" for Combined.
───────────────────────────────────────────────────────────────────────────
REFERENCE 94
──────────────────────────────────────────────────────────────────────
Type :29
Name :Move a File
Optional Data :<Full Source Path>
Comparative :Same as RA
This function is intended to be a sysop maintenance function. This allows the
user move files from specified area (<Full Source Path>) to any DOS directory
without the need to drop to DOS. After the file has been copied you have the
option of transferring the description of the file to the same location.
───────────────────────────────────────────────────────────────────────────
Type :30
Name :Directory
Optional Data :<Full Path> or /F
Comparative :Same as RA
Display a DOS directory listing of the directory in the optional data showing
the file names, size, and date of each file. The user is optionally prompted
to enter a wildcard to look for matching files.
You may use the parameter /F if you are using the Menu Templating System.
───────────────────────────────────────────────────────────────────────────
Type :31
Name :List files
Optional Data :<Full Path> or /F
Comparative :Same as RA
This menu type shows a list of files that are available for downloading. The
file names and descriptions are written in the FILES.BBS. The file can easily
be written by converting the DOS directory to file by typing "dir >
files.bbs". Any uploads from now on are automatically appended to this file.
File descriptions are limited to 255 characters and word wrapping is
automatic. A "*" denotes that a file is new since the last time the user has
called.
You may use the parameter /F if you are using the Menu Templating System
───────────────────────────────────────────────────────────────────────────
Type :32
Name :Download a File From Area
Optional Data :<Full Path> or /F [Password]
Comparative :Same as RA
Enables the user to download a file in the specified directory whether or not
the file is listed in the FILES.BBS. If the password option is used, the user
will be prompted for a password before access is granted.
If the user uses a wildcard they will be prompted individually for each file
that matches the wildcard asking if they would like to download.
You may use the parameter /F if you are using the Menu Templating System.
───────────────────────────────────────────────────────────────────────────
REFERENCE 95
──────────────────────────────────────────────────────────────────────
Type :33
Name :Upload a File
Optional Data :<Full Path> or /F
Comparative :Same as RA
Allows the user to upload a file. The file will reside in the specified
directory of the current directory. The description of the file will
automatically be added to the FILES.BBS in the appropriate directory.
If you choose to put /F PF with automatically put the current menu template in
the selected file area
───────────────────────────────────────────────────────────────────────────
Type :34
Name :View Archive
Optional Data :<Full Path> or /F
Comparative :Same as RA
Allows the user to view the file contained within an archive. The following
archives are supported: ARC, ARJ, LHA, LZH, PAK, LHA, LZH.
If you choose to put /F Proflex will automatically put the current menu
template in the selected file area
───────────────────────────────────────────────────────────────────────────
Type :35
Name :File Scan by Keyword
Optional Data :N/A
Comparative :Same as RA
This function searches all of the FILES.BBS in the file areas the user has
access or the file areas they specify and look for matches in the file name
and description.
───────────────────────────────────────────────────────────────────────────
Type :36
Name :File Scan by Filename
Optional Data :N/A
Comparative :Same as RA
Same as type 35 but only looks for matches in the file name.
───────────────────────────────────────────────────────────────────────────
Type :37
Name :Show New Files
Optional Data :N/A
Comparative :Same as RA
Looks at all of the file areas that the user may access and compares the dates
of the files to the date the user enters. The default is to search for new
files since the user as last called the board.
───────────────────────────────────────────────────────────────────────────
REFERENCE 96
──────────────────────────────────────────────────────────────────────
Type :38
Name :View a Text File
Optional Data :<Full Path> or /F
Comparative :Same as RA
Lets the user view the contents of a ASCII/ANSI file in the specified or
current directory.
If you choose to put /M Proflex will automatically put the current menu
template in the selected message area
───────────────────────────────────────────────────────────────────────────
Type :39
Name :Display a Fully Named Text File
Optional Data :<Full Path and Name>
Comparative :Same as RA
Exactly like menu type 5, but you are allowed to choose a full path.
───────────────────────────────────────────────────────────────────────────
Type :40
Name :Display an ASC/ANS text file with hotkeys active
Optional Data :<1-8 character name>
Comparative :Same as RA
Exactly like menu type 5, but hot keys are active. Menu may be used to create
menu screens that contain graphics while leaving the hotkeys available to
accept commands.
───────────────────────────────────────────────────────────────────────────
Type :41
Name :Toggle Full Screen Editor
Optional Data :N/A
Comparative :Same as RA
Give the user the option to toggle the full screen editor either on or off.
The full screen editor is only available to a user that has ANSI graphics
available.
───────────────────────────────────────────────────────────────────────────
Type :42
Name :Toggle Hot Keys
Optional Data :N/A
Comparative :Same as RA
Gives the user the option of either using hot keys or command stacking mode
which is several commands on one line separated by semicolons.
───────────────────────────────────────────────────────────────────────────
REFERENCE 97
──────────────────────────────────────────────────────────────────────
Type :43
Name :New Mail {+}
Optional Data :N/A
Comparative :Same as RA
Show a list of all the area the user has access to and highlights the areas
that contain unread messages.
───────────────────────────────────────────────────────────────────────────
Type :44
Name :Reset Combined Area Settings
Optional Data :N/A
Comparative :Same as RA
Lets the user turn on or off the available message areas for their combined
message area settings.
───────────────────────────────────────────────────────────────────────────
Type :45
Name :Display a Text File and Wait
Optional Data :<1-8 character name>
Comparative :Same as RA
Same as menu type 5, but wait for [Return] to be pressed before continuing.
This is especially helpful function for displaying files that are generated
by utilities that don't add a Ctrl-A (Press [Enter] To Continue) at the end
of the file.
───────────────────────────────────────────────────────────────────────────
Type :46
Name :Display Direct Text File with CR
Optional Data :<Full Path and Name>
Comparative :Same as RA
Same as menu type 45, but allows you to enter a full path and name.
───────────────────────────────────────────────────────────────────────────
Type :47
Name :Make a Log Entry
Optional Data :<Log Entry Name>
Comparative :Same as RA
This menu type takes the contents of the optional data in every menu type that
the user encounters while online and appends them to a specified log file.
───────────────────────────────────────────────────────────────────────────
REFERENCE 98
──────────────────────────────────────────────────────────────────────
Type :48
Name :Download a Specific File
Optional Data :<Full Path and Name>
Comparative :Same as RA
Allows the user to download a file that you specify using the protocol of
their choose. Useful if you would like to make a text file containing all the
files on your bbs that can be down loaded easy for the user to download. If a
wildcard is used in the optional data field the user must have a protocol that
can handle batch transfers.
───────────────────────────────────────────────────────────────────────────
Type :49
Name :Select Message Area
Optional Data :N/A
Comparative :Same as RA
Shows the user a list of the message bases that they have access to and
prompts the users to select a message area by entering a number that
corresponds to the area. The numbers that are assigned to the message area are
defined in PFCONFIG.
───────────────────────────────────────────────────────────────────────────
Type :50
Name :Select a File Area
Optional Data :N/A
Comparative :Same as RA
Same as menu type 49 with the exception of taking the user to a file area as
opposed to a message area.
───────────────────────────────────────────────────────────────────────────
Type :51
Name :List Today's Callers
Optional Data :N/A
Comparative :Same as RA
Lists users that have called your board since midnight including their log on
and off times, baud rate, and what node the called.
───────────────────────────────────────────────────────────────────────────
Type :52
Name :List Users On Line
Optional Data :N/A
Comparative :Same as RA
Shows the user a list of all the people who are currently connected to the
other nodes. This is useful to user of a multi-node system where the user
might what to chat with another user online. In addition to their name, their
location, baud rate, and location are shown.
───────────────────────────────────────────────────────────────────────────
REFERENCE 99
──────────────────────────────────────────────────────────────────────
Type :53
Name :Toggle "Do Not Disturb"
Optional Data :N/A
Comparative :Same as RA
This another multi-line feature only. It allows the user turn on or off
the ability of other users to send them messages with the type 54
function, like - "Hey Joe, I noticed that you're online 3. Wanna chat?"
Note that the sysop has the ability to override this and send a message
anyway.
───────────────────────────────────────────────────────────────────────────
Type :54
Name :
Optional Data :N/A
Comparative :Same as RA
Allows the user to send a message to another user who is logged currently
on another line. If the other user has not turned on their "do not disturb"
flag, the sender will be prompted for a one line message to send to the
user. Depending on what the person you are sending the message is doing when
you send the message will get the message ten to fifteen seconds later. If
they are downloading a file it will take longer.
───────────────────────────────────────────────────────────────────────────
Type :55
Name :Download any File
Optional Data :N/A
Comparative :Same as RA
This is the most powerful download function available and should be only
accessible by the sysop. It allows the user to download any file from any
valid DOS directory on any drive using any of the available file transfer
protocols. Note that this download function does not look at download limits,
file ratios or transfer time, and does not update the users record to reflect
the download.
───────────────────────────────────────────────────────────────────────────
Type :56
Name :Browse the nodelist {+}
Optional Data :None
Comparative :Same as RA
Allows the user to browse the nodelist. Includes functions to list all
zones, list all nets and regions in a zone, and list all nodes in a net or
region.
───────────────────────────────────────────────────────────────────────────
REFERENCE 100
──────────────────────────────────────────────────────────────────────
Type :57
Name :Change home/voice number
Optional Data :None
Comparative :Same as RA
Allows the user to change their home/voice phone number.
───────────────────────────────────────────────────────────────────────────
Type :58
Name :Change business/data number
Optional Data :None
Comparative :Same as RA
Allows the user to change their business/data phone number.
───────────────────────────────────────────────────────────────────────────
Type :59
Name :Global Download
Optional Data :None
Comparative :Same as RA
Allows the user to download from any file area.
───────────────────────────────────────────────────────────────────────────
Type :60
Name :Change Handle
Optional Data :None
Comparative :Same as RA
Allows the user to change their handle.
───────────────────────────────────────────────────────────────────────────
Type :61
Name :Toggle Avatar
Optional Data :None
Comparative :Same as RA
Allows the user to change toggle Avatar video on/off.
───────────────────────────────────────────────────────────────────────────
Type :62
Name :Toggle full screen message viewer
Optional Data :None
Comparative :Same as RA
Allows the user to toggle the use of the full screen message viewer on/off.
───────────────────────────────────────────────────────────────────────────
REFERENCE 101
───────────────────────────────────────────────────────────────────────────
S y s o p k e y s
───────────────────────────────────────────────────────────────────────────
The following keys work while a user is online:
[ALT-C] : Break in for a chat if there is a user on remotely.
ESC finishes chat mode and drops the user back to the BBS
[ALT-H] : Hang up on the user immediately.
[ALT-J] : Drop to a DOS while the user is still online.
[Up-Arrow] : Increases the user's time by one minute.
[Down-Arrow] : Decreases the user's time by one minute.
REFERENCE 102
──────────────────────────────────────────────────────────────────────
T e x t f i l e s C o n t r o l C o d e s
──────────────────────────────────────────────────────────────────────
* System Control Codes
----------------------
Visual
Char. Representa-
ASCII# Combo. -tion Information displayed
------ ----- ------ --------------------------------------
01 ^A = Wait until the [Return] key is pressed
02 ^B = Disable aborting with the "S" key
03 ^C = Enable aborting with the "S" key
04 ^D = Enable the "Continue?" prompt
05 ^E = Disable the "Continue?" prompt
06 ^F = * Insert a user parameter
07 ^G = Produce a beep on the caller's console
08 ^H = X Backspace
09 ^I = X Tab (forward 8 characters)
10 ^J = X Linefeed
11 ^K = * Insert a system parameter
12 ^L = X Clear screen
13 ^M = X Carriage return
17 ^Q = X RESERVED FOR XON/XOFF HANDSHAKING
19 ^S = X RESERVED FOR XON/XOFF HANDSHAKING
23 ^W = Pause for one second
24 ^X = * Execute a program in a DOS shell
26 ^Z = X END OF FILE MARKER. DON'T USE THIS!
----------------------------------------------------------------------
NOTE: "X" denotes a character which is unable to be displayed in this
text file because it would perform it's intended function.
REFERENCE 103
──────────────────────────────────────────────────────────────────────
T e x t f i l e s C o n t r o l C o d e s
──────────────────────────────────────────────────────────────────────
* User Control Codes
───────────────────────────────────────────────
Visual
Char. Representa-
ASCII# Combo. -tion Information Displayed
───────────────────────────────────────────────
65 ^FA = A Users full name
66 ^FB = B Location
67 ^FC = C Password
68 ^FD = D Business/Data phone number
69 ^FE = E Voice/Home phone number
70 ^FF = F Date of last call
71 ^FG = G Time of last call
72 ^FH = H A Flags setting
73 ^FI = I B Flags setting
74 ^FJ = J C Flags setting
75 ^FK = K D Flags setting
76 ^FL = L NetMail credit remaining (cents)
77 ^FM = M Total messages posted
78 ^FN = N Last message read
79 ^FO = O Security level
80 ^FP = P Total calls to the BBS
81 ^FQ = Q Number of uploads
82 ^FR = R Kilobytes of uploads
83 ^FS = S Number of downloads
84 ^FT = T Kilobytes of downloads
85 ^FU = U Minutes used today
86 ^FV = V Current screen length
87 ^FW = W First name only
88 ^FX = X ANSI setting (ON/OFF)
89 ^FY = Y "Continue?" prompt setting (ON/OFF)
90 ^FZ = Z Screen clearing (ON/OFF)
48 ^F0 = 0 Full screen editor (ON/OFF)
49 ^F1 = 1 Quiet/do not disturb mode (ON/OFF)
50 ^F2 = 2 Hot-Keys (ON/OFF)
51 ^F3 = 3 Handle
52 ^F4 = 4 Date of first call
53 ^F5 = 5 Date of birth
54 ^F6 = 6 Subscription expiry date
55 ^F7 = 7 Days until subscription expire
56 ^F8 = 8 AVATAR setting (ON/OFF)
57 ^F9 = 9 File ratio (number of files)
58 ^F: = : File ratio (kilobytes)
59 ^F; = ; Full screen message viewer (ON/OFF)